CVE-2026-43867: CWE-502 Deserialization of Untrusted Data in Apache Software Foundation Apache Camel
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.
AI Analysis
Technical Summary
The vulnerability in Apache Camel's PQC component involves insecure deserialization of metadata stored in AWS Secrets Manager. The AwsSecretsManagerKeyLifecycleManager.deserializeMetadata() method reads Base64-decoded serialized objects using java.io.ObjectInputStream.readObject() without applying ObjectInputFilter or class allow-listing, allowing any side effects in the deserialized object's readObject() method to execute before type checks. An attacker with permission to write to the AWS Secrets Manager secret (secretsmanager:PutSecretValue) can store malicious serialized objects that lead to potential code execution within the application context. This vulnerability affects Apache Camel versions 4.18.0 up to but not including 4.18.3, and 4.19.0 up to but not including 4.21.0. The issue is related to and fixed alongside CVE-2026-46590 and CVE-2026-40048. The recommended remediation is upgrading to Apache Camel 4.18.3 or 4.21.0. For those unable to upgrade immediately, applying least-privilege IAM policies to restrict write access to the AWS Secrets Manager secret is advised.
Potential Impact
Successful exploitation requires write permissions to the AWS Secrets Manager secret holding the PQC key metadata. An attacker with such permissions can supply crafted serialized objects that execute arbitrary code during deserialization, potentially compromising the application managing the keys. This could lead to unauthorized code execution within the application's runtime environment.
Mitigation Recommendations
A fix is available in Apache Camel versions 4.18.3 and 4.21.0; users should upgrade to these versions to remediate the vulnerability. For deployments unable to upgrade immediately, restrict write access to the AWS Secrets Manager secret containing the PQC key metadata by enforcing least-privilege IAM policies so that only the application’s own identity has secretsmanager:PutSecretValue permission. Additionally, keep PQC key material in a secret separate from any data writable by less-trusted principals.
CVE-2026-43867: CWE-502 Deserialization of Untrusted Data in Apache Software Foundation Apache Camel
Description
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.
CVSS v3.1
Score 9.8critical
Affected software
pkg:maven/Apache Software Foundation/org.apache.camel:camel-pqcRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in Apache Camel's PQC component involves insecure deserialization of metadata stored in AWS Secrets Manager. The AwsSecretsManagerKeyLifecycleManager.deserializeMetadata() method reads Base64-decoded serialized objects using java.io.ObjectInputStream.readObject() without applying ObjectInputFilter or class allow-listing, allowing any side effects in the deserialized object's readObject() method to execute before type checks. An attacker with permission to write to the AWS Secrets Manager secret (secretsmanager:PutSecretValue) can store malicious serialized objects that lead to potential code execution within the application context. This vulnerability affects Apache Camel versions 4.18.0 up to but not including 4.18.3, and 4.19.0 up to but not including 4.21.0. The issue is related to and fixed alongside CVE-2026-46590 and CVE-2026-40048. The recommended remediation is upgrading to Apache Camel 4.18.3 or 4.21.0. For those unable to upgrade immediately, applying least-privilege IAM policies to restrict write access to the AWS Secrets Manager secret is advised.
Potential Impact
Successful exploitation requires write permissions to the AWS Secrets Manager secret holding the PQC key metadata. An attacker with such permissions can supply crafted serialized objects that execute arbitrary code during deserialization, potentially compromising the application managing the keys. This could lead to unauthorized code execution within the application's runtime environment.
Mitigation Recommendations
A fix is available in Apache Camel versions 4.18.3 and 4.21.0; users should upgrade to these versions to remediate the vulnerability. For deployments unable to upgrade immediately, restrict write access to the AWS Secrets Manager secret containing the PQC key metadata by enforcing least-privilege IAM policies so that only the application’s own identity has secretsmanager:PutSecretValue permission. Additionally, keep PQC key material in a secret separate from any data writable by less-trusted principals.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-04T11:46:36.123Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
- Is Cloud Service
- true
Threat ID: 6a4b6cac27e9c79719252285
Added to database: 07/06/2026, 08:51:56 UTC
Last enriched: 07/06/2026, 09:21:43 UTC
Last updated: 07/06/2026, 23:08:18 UTC
Views: 10
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.