CVE-2026-46590
Received Received - Intake

Deserialization of Untrusted Data in Apache Camel PQC

Publication date: 2026-07-06

Last updated on: 2026-07-06

Assigner: Apache Software Foundation

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-06
Last Modified
2026-07-06
Generated
2026-07-06
AI Q&A
2026-07-06
EPSS Evaluated
N/A
NVD
CVE-2026-46590
EUVD
EUVD-2026-41834

Affected Vendors & Products

Showing 4 associated CPEs
Vendor Product Version / Range
apache camel to 4.18.3 (exc)
apache camel to 4.21.0 (exc)
apache camel 4.21.0
apache camel 4.18.3

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-502 The product deserializes untrusted data without sufficiently ensuring that the resulting data will be valid.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-46590 is a security vulnerability in the Apache Camel camel-pqc component involving deserialization of untrusted data. The vulnerability arises because certain key-lifecycle managers (HashiCorp Vault and AWS Secrets Manager) deserialize Base64-wrapped key metadata using java.io.ObjectInputStream.readObject() without applying any ObjectInputFilter or class allow-list. This means that if an attacker can write a crafted serialized object to the backend storage, it can trigger code execution during deserialization before type checks occur.

This issue is a follow-on to a previous vulnerability (CVE-2026-40048) that partially addressed similar risks but did not fully secure all key-lifecycle managers or legacy migration paths. The vulnerability affects Apache Camel versions from 4.18.0 before 4.18.3 and from 4.19.0 before 4.21.0.

Impact Analysis

If exploited, this vulnerability can lead to remote code execution within the context of the application managing the keys. An attacker who has write access to the operator-controlled backend (such as the HashiCorp Vault KV path or AWS Secrets Manager secret) can store a malicious serialized object that executes arbitrary code when deserialized during normal key lifecycle operations.

This can compromise the security of the application, potentially allowing unauthorized actions, data breaches, or further system compromise.

Mitigation Strategies

To mitigate this vulnerability immediately, users should upgrade Apache Camel to version 4.21.0 or, if using the 4.18.x LTS stream, upgrade to 4.18.3.

If upgrading immediately is not possible, restrict write access to the key backend so that only the application's own identity can write the camel-pqc secrets.

  • Implement least-privilege HashiCorp Vault policies.
  • Restrict AWS Secrets Manager permissions, specifically the secretsmanager:PutSecretValue IAM action.

Keep the post-quantum cryptography (PQC) key material in a backend separate from any data that less-trusted principals can write.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-46590. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart