# CVE-2026-46590: Apache Camel-PQC: The HashiCorp Vault and AWS Secrets Manager key-lifecycle managers deserialize persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter (incomplete remediation of CVE-2026-40048) > An attacker with write access to the key backend can execute arbitrary code via unsafe deserialization in Apache Camel's PQC component. - **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jul 2026 - **Updated:** 6 Jul 2026 - **Also known as:** GHSA-857v-xvh8-7hjc ## What is CVE-2026-46590? CVE-2026-46590 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. HashicorpVaultKeyLifecycleManager and AwsSecretsManagerKeyLifecycleManager read that metadata back from the configured secret backend by deserializing a Base64-wrapped value 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. The same unfiltered legacy-migration read also remained in FileBasedKeyLifecycleManager (for the stored KeyPair and KeyMetadata). A principal who can write to the operator-controlled backend that holds these values - the HashiCorp Vault KV path, or the AWS Secrets Manager secret (requiring a Vault token or secretsmanager:PutSecretValue) - 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 an incomplete-remediation follow-on to CVE-2026-40048 (CAMEL-23200), which changed FileBasedKeyLifecycleManager to store metadata as JSON / PKCS#8 / X.509 but did not add an ObjectInputFilter, did not cover the Vault and AWS sibling managers, and left FileBasedKeyLifecycleManager's own legacy-migration deserialization unfiltered. 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 key backend so that only the application's own identity can write the camel-pqc secrets (least-privilege HashiCorp Vault policies and secretsmanager:PutSecretValue IAM), and keep the PQC key material in a backend separate from any data that less-trusted principals can write. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2026-46590? 4 open source packages ship an affected version, including org.apache.camel:camel-pqc. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-pqc` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-pqc` | Maven | From 4.18.0 | 4.18.3 | | `org.apache.camel:camel-pqc` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-pqc` | Maven | From 4.19.0 | 4.21.0 | Products: Apache Camel. ## How do I fix CVE-2026-46590? Upgrade org.apache.camel:camel-pqc to a fixed version for your release line: 4.18.3 or 4.21.0. ## Is CVE-2026-46590 being exploited? There is no known exploitation of CVE-2026-46590 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-46590: Apache Camel camel-pqc key-lifecycle unsafe deserialization (FileBasedKeyLifecycleManager legacy .key migration via ObjectInputStream), incomplete remediation of CVE-2026-40048 (fixed in 4.18.3/4.21.0) (github_poc): https://github.com/oscerd/CVE-2026-46590 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-46590 and fix it if it is affected. What it is: CVE-2026-46590 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 6 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-46590 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-pqc (Maven): affected from 4.18.0; fixed in 4.18.3 - org.apache.camel:camel-pqc (Maven): affected from 4.18.0; fixed in 4.18.3 - org.apache.camel:camel-pqc (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-pqc (Maven): affected from 4.19.0; fixed in 4.21.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-46590/ (Markdown: https://insights.sbomify.com/CVE-2026-46590/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46590 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46590 - OSV: https://osv.dev/vulnerability/CVE-2026-46590 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-46590/ Summaries are generated and may contain mistakes; the official description above is the record.