What is the CVSS score of CVE-2026-46590?

CVE-2026-46590 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.2%.

Which versions of Apache Camel are affected by CVE-2026-46590?

Apache Camel's post-quantum cryptography key management component (versions 4.18.0-4.18.2, 4.19.0-4.20.x) contains a high-severity remote code execution vulnerability exploitable by actors with…. A patch is available.

How to fix or mitigate CVE-2026-46590?

Within 24 hours: Inventory systems running Apache Camel 4.18.0-4.18.2 and 4.19.0-4.20.x; verify whether CVE-2026-40048 patches are deployed; assess key backend write-access controls. Within 7 days: Apply vendor-released patch to all affected systems and validate upgrade completion. Within 30 days: Audit backend access controls, review key lifecycle operation logs, and implement enhanced monitoring.

Apache Camel CVE-2026-46590

EUVD-2026-41834 HIGH

Deserialization of Untrusted Data (CWE-502)

2026-07-06 apache

GHSA-857v-xvh8-7hjc

Deserialization Hashicorp RCE Apache Apache Camel

8.8

CVSS 3.1 · Vendor: apache

Severity by source

Vendor (apache) PRIMARY

8.8 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

vuln.today AI

7.2 HIGH

Requires privileged write access to the operator-controlled Vault/Secrets Manager backend, so PR:H over the network (AV:N); successful deserialization yields full C/I/A compromise of the key-management app.

3.1 AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

4.0 AV:N/AC:H/AT:P/PR:H/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (apache).

CVSS VectorVendor: apache

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Updated

Jul 06, 2026 - 21:29 vuln.today

v5 (cvss_changed)

Analysis Updated

Jul 06, 2026 - 21:28 vuln.today

v4 (cvss_changed)

Analysis Updated

Jul 06, 2026 - 21:28 vuln.today

v3 (cvss_changed)

Analysis Updated

Jul 06, 2026 - 21:27 vuln.today

v2 (cvss_changed)

Re-analysis Queued

Jul 06, 2026 - 20:22 vuln.today

cvss_changed

CVSS changed

Jul 06, 2026 - 20:22 NVD

8.8 (HIGH)

Patch available

Jul 06, 2026 - 10:01 EUVD

Analysis Generated

Jul 06, 2026 - 09:40 vuln.today

Blast Radius

ecosystem impact

† from your stack dependencies † transitive graph · vuln.today resolves 4-path depth

3 maven packages depend on org.apache.camel:camel-pqc (2 direct, 1 indirect)

Ecosystem-wide dependent count for version 4.18.0.

DescriptionCVE.org

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.

Articles & Coverage 2

News 3 New HashiCorp Vulnerabilities - 1 Critical, 2 High Severity Jul 07, 2026 News 3 New HashiCorp Vulnerabilities - 1 Critical, 2 High Severity Jul 06, 2026

AnalysisAI

Remote code execution via unsafe Java deserialization affects the camel-pqc component of Apache Camel 4.18.0-4.18.2 and 4.19.0-4.20.x. The HashiCorp Vault and AWS Secrets Manager KeyLifecycleManager implementations (and a legacy-migration path in the file-based manager) read post-quantum key metadata back with a raw ObjectInputStream.readObject() lacking any ObjectInputFilter or allow-list, so a principal able to write to the key backend can plant a gadget object that executes during normal key-lifecycle operations. No public exploit has been identified at time of analysis and EPSS is low (0.19%), but SSVC rates technical impact as total; this is an incomplete-remediation follow-on to CVE-2026-40048.