Skip to main content
VulnerabilityPublished

CVE-2026-43867: Apache Camel · Deserialization of Untrusted Data

Affects Apache CamelSource CVE Database V5

0
Compare

Mentioned vulnerabilities

Not known to be exploited · CVSS 9.8 Critical : upgrade to 4.21.0 or 4.18.3 as a priority.

Data as of 19 Nov 2026, 20:25 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.9% chance of exploitation in 30 days – higher than 61% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.21.0, 4.18.3
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 19 Nov 2026.

What to do

Upgrade Apache to 4.21.0 or 4.18.3.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache CamelAffected
  • >=4.19.0 <4.21.0
Fixed in
  • 4.21.0
Apache Software FoundationApache CamelAffected
  • >=4.18.0 <4.18.3
Fixed in
  • 4.18.3
MavenApache Software Foundation/org.apache.camel:camel-pqcpkg:maven/Apache Software Foundation/org.apache.camel:camel-pqcOther threatsAffected
  • >=4.18.0 <4.18.3
  • >=4.19.0 <4.21.0
Fixed in
  • 4.18.3
  • 4.21.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

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.

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.

References

Community reviews

Loading reviews…