CVE-2026-46590

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.

• CWE-502

• https://camel.apache.org/security/CVE-2026-46590.htmlVendor Advisory

Published

Jul 6, 2026

Last Modified

Jul 8, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-46584Improper Input Validation, Exposure of Sensitive Information…3.7
• CVE-2026-46585Improper Input Validation, Authorization Bypass Through User…7.5
• CVE-2026-46586Improper Control of Generation of Code ('Code Injection'), I…8.8
• CVE-2026-46587Improper Input Validation vulnerability in Apache Camel. Th…7.3
• CVE-2026-46588Improper Input Validation vulnerability in Apache Camel. Th…7.3
• CVE-2026-4659The Unlimited Elements for Elementor plugin for WordPress is…7.5
• CVE-2026-46591Improper Neutralization of Special Elements in Data Query Lo…8.2
• CVE-2026-46592Improper Input Validation, Unintended Proxy or Intermediary …7.5
• CVE-2026-46593A SQL injection vulnerability has been identified in the PHP…8.6
• CVE-2026-46594A reflected cross-site scripting (XSS) vulnerability has bee…5.1
• CVE-2026-46595Previously, CVE-2024-45337 fixed an authorization bypass for…10
• CVE-2026-46597An incorrectly placed cast from bytes to int allowed for ser…7.5