CVE-2026-46590: Apache Camel deserialization of untrusted data in PQC component

CVE-2026-46590 · Severity: high · CVSS 8.8 · Published 2026-07-06

Apache Camel's post-quantum cryptography (PQC) component insecurely deserializes key metadata stored in HashiCorp Vault and AWS Secrets Manager using Java's ObjectInputStream without any input validation. An attacker with write access to these secret backends could inject a malicious serialized object that executes arbitrary code when the application loads the key, compromising the security of applications managing post-quantum keys for encrypted communications.

Technologies: Apache Camel, org.apache.camel:camel-pqc (Maven). Vendors: Apache, Maven.

Quick answers

Is CVE-2026-46590 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46590 being exploited in the wild.
How severe is CVE-2026-46590?
High severity, with a CVSS score of 8.8, published 6 July 2026.
Which products and versions are affected?
Apache Camel 4.18.0 to 4.18.2, 4.19.0 to 4.20.x; Apache Camel PQC component 4.18.0 to 4.18.2, 4.19.0 to 4.20.x; org.apache.camel:camel-pqc (Maven) ECOSYSTEM:introduced=4.18.0,fixed=4.18.3.
Is there a fix for CVE-2026-46590?
Yes. org.apache.camel:camel-pqc (Maven): upgrade to 4.18.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46590 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-46590?
Check whether you run Apache Camel, Apache Camel PQC component or org.apache.camel:camel-pqc (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.camel:camel-pqc (Maven): upgrade to 4.18.3 or later
    # set org.apache.camel:camel-pqc to 4.18.3 in your pom.xml or build.gradle

Technical details

The vulnerability is a deserialization-of-untrusted-data flaw (CWE-502) in Apache Camel's camel-pqc component. The HashicorpVaultKeyLifecycleManager and AwsSecretsManagerKeyLifecycleManager classes deserialize Base64-wrapped KeyMetadata objects using raw java.io.ObjectInputStream.readObject() calls without an ObjectInputFilter or class allow-list. Because the cast to KeyMetadata occurs only after deserialization completes, any gadget chain executed during readObject() runs before type validation, enabling arbitrary code execution. The same vulnerable pattern exists in FileBasedKeyLifecycleManager's legacy migration code. Exploitation requires write access to the backend (HashiCorp Vault KV path or AWS Secrets Manager secret), but does not require authentication to the application itself. The vulnerability is a follow-on to CVE-2026-40048, which partially addressed FileBasedKeyLifecycleManager but left it and the AWS/Vault managers unprotected. Patches are available in versions 4.18.3 (LTS) and 4.21.0 (current).

Affected products

  • Apache Camel 4.18.0 to 4.18.2, 4.19.0 to 4.20.x
  • Apache Camel PQC component 4.18.0 to 4.18.2, 4.19.0 to 4.20.x

Identifiers

  • CVE-2026-46590
  • GHSA-857v-xvh8-7hjc

Timeline

  • 2026-07-06: disclosed: Published to GitHub Advisory Database and NVD
  • 2026-07-06: patched: Version 4.18.3 and 4.21.0 released with fixes

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.