CVE-2026-43867: Apache Camel: Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter
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.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
Apache Camel: Camel-PQCto a version that resolves this vulnerability.Fixed in 4.18.3 - Upgrade
Upgrade
Apache Camel: Camel-PQCto a version that resolves this vulnerability.Fixed in 4.21.0 - Compensating control
Restrict write access to the AWS Secrets Manager secret that holds the camel-pqc key metadata so only the application’s own identity has secretsmanager:PutSecretValue on that secret (least-privilege IAM), and keep the PQC key material in a separate secret that less-trusted principals cannot write.
Event History
Frequently Asked Questions
What is the severity of CVE-2026-43867?
CVE-2026-43867 has a risk rating of 62, indicating a medium severity level.
How do I fix CVE-2026-43867?
To fix CVE-2026-43867, update to the latest version of Apache Camel that addresses this vulnerability.
What type of vulnerability is CVE-2026-43867?
CVE-2026-43867 is a Deserialization of Untrusted Data vulnerability affecting the Apache Camel PQC Component.
Which component of Apache Camel is affected by CVE-2026-43867?
CVE-2026-43867 affects the camel-pqc component of Apache Camel.
What does the AWS Secrets Manager key-lifecycle manager do in relation to CVE-2026-43867?
The AWS Secrets Manager key-lifecycle manager in CVE-2026-43867 deserializes persisted key metadata using java.io.ObjectInputStream, which is the source of the vulnerability.