CVE-2026-43867

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. 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.

• CWE-502

• https://camel.apache.org/security/CVE-2026-43867.html

Published

Jul 6, 2026

Last Modified

Jul 6, 2026

Status

Undergoing Analysis

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-43861mutt before 2.3.2 does not check for '\0' in url_pct_decode.3.7
• CVE-2026-43862In mutt before 2.3.2, the imap_auth_gss security level is mi…3.7
• CVE-2026-43863mutt before 2.3.2 has an infinite loop in data_object_to_str…3.7
• CVE-2026-43864mutt before 2.3.2 has a show_sig_summary NULL pointer derefe…2.5
• CVE-2026-43865Deserialization of Untrusted Data vulnerability in Apache Ca…8.1
• CVE-2026-43866Deserialization of Untrusted Data vulnerability in Apache Ca…7.3
• CVE-2026-43868Memory Allocation with Excessive Size Value vulnerability in…5.3
• CVE-2026-43869Improper Validation of Certificate with Host Mismatch vulner…7.3
• CVE-2026-4387StrongDM Desktop Application before 23.74.0 (Desktop Client …2
• CVE-2026-43870Origin Validation Error, Improper Limitation of a Pathname t…7.3
• CVE-2026-43871Loop with Unreachable Exit Condition ('Infinite Loop') vulne…7.5
• CVE-2026-43872Actual is an open-source personal finance application. Prior…5.3