Critical [CVE-2026-40048 +2] Deserialization of Untrusted Data vulnerability in Apache Camel PQC Component
This critical-severity Apache Software Foundation advisory covers CVE-2026-43867 and CVE-2026-40048 and 1 more CVE affecting Apache Camel PQC.
Aggregated and source-linked by VulniPulse. Data sources, validation and limitations. This bulletin covers 3 CVEs; its score, affected versions and guidance may apply to different issues within that bulletin.
VulniPulse record published Record updated
Android app · Google Play
Monitor future Apache Software Foundation CVEs from your phone.
Choose a whole vendor or a precise platform, then receive matching security advisories by phone notification, email, or both. Coverage follows 34 official vendor sources and 160+ reviewed platform categories.
Summary
Deserialization of Untrusted Data vulnerability in Apache Camel PQC Component. The camel-pqc component persists post-quantum key metadata (KeyMetadata) through pluggable KeyLifecycleManager implementations.
AwsSecretsManagerKeyLifecycleManager.deserializeMetadata() reads that metadata back from the configured AWS Secrets Manager secret by Base64-decoding the stored value and deserializing it with a raw java.io.ObjectInputStream.readObject() and no ObjectInputFilter or class allow-list; the cast to KeyMetadata happens only after readObject() returns, so any readObject() side effects in a crafted object run before the type check.
A principal who can write to the AWS Secrets Manager secret that holds this metadata (requiring secretsmanager:PutSecretValue on that secret) could store a crafted serialized object that is deserialized during normal key-lifecycle operations, potentially leading to code execution in the context of the application that manages the keys.
This is the same underlying defect, in the same code path and remediated by the same fix, as CVE-2026-46590, which was reported independently and additionally covers the HashiCorp Vault and file-based sibling managers; both are incomplete-remediation follow-ons to CVE-2026-40048 (CAMEL-23200).
This issue affects Apache Camel: from 4.18.0 before 4.18.3, from 4.19.0 before 4.21.0.
- 4.18.0 through 4.18.3
- 4.19.0 through 4.21.0.
Official advisory · high-confidence parse· fetched 3 months ago·verify at source
- 4.21.0
- 4.18.3
Official advisory · high-confidence parse· fetched 3 months ago·verify at source
Mitigation checklist
- Users are recommended to upgrade to version 4.21.0, which fixes the issue.
- If users are on the 4.18.x LTS releases stream, then they are suggested to upgrade to 4.18.3.
- For deployments that cannot upgrade immediately, restrict write access to the AWS Secrets Manager secret that holds the camel-pqc key metadata so that only the application’s own identity holds secretsmanager:PutSecretValue on it (least-privilege IAM), and keep the PQC key material in a secret separate from any data that less-trusted principals can write.
Official advisory · high-confidence parse· fetched 3 months ago·verify at source
Discussion(0)
No comments yet. Share field notes, upgrade gotchas, or questions — verify against the vendor advisory before acting on community advice.
Sign in to join the discussion.