Skip to content
VulniPulse
High7.8Apache Software Foundation

CVE-2026-40048: Apache Camel PQC: Unsafe Deserialization from FileBasedKeyLifecycleManager

This Apache advisory covers CVE-2026-40048 in Apache Camel.

Open the Apache advisory

Key facts

Vendor rating
High, CVSS 7.8
CVSS vector
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H · base score 7.8, scored by CISA-ADPAttack vector: local. Attack complexity: low. Privileges required: low. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: high. Availability impact: high.
Weakness
  • CWE-502 Deserialization of Untrusted Data
EPSS
0.33% chance of exploitation in the next 30 days (26th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: no. Technical impact: total. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
Apache Camel PQC 4.19.0 before 4.20.0; Apache Camel PQC 4.18.0 before 4.18.2
Fixed in
4.20.0, 4.18.2
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationMessaging

Description

The Camel-PQC FileBasedKeyLifecycleManager class deserializes the contents of `.key` files in the configured key directory using java.io.ObjectInputStream without applying any ObjectInputFilter or class-loading restrictions. The cast to `java.security.

KeyPair` is evaluated only after `readObject()` has already returned, so any `readObject()` side effects in the deserialized object run before the type check.

An attacker who can write to the key directory used by a Camel application — for example through a path traversal into the directory, misconfigured filesystem permissions on the volume where keys are stored, a compromised key provisioning pipeline, or a symlink attack — can place a crafted serialized Java object that, when deserialized during normal key lifecycle operations, results in arbitrary code execution in the context of the application.

This issue affects Apache Camel: from 4.19.0 before 4.20.0, from 4.18.0 before 4.18.2. Users are recommended to upgrade to version 4.20.0, which fixes the issue by replacing java.io.ObjectInputStream-based key and metadata storage with standard PKCS#8 (private key) / X.509 SubjectPublicKeyInfo (public key) Base64 JSON encoding.

For users on the 4.18.x LTS releases stream, upgrade to 4.18.2. Affected product named by the advisory: Apache Camel PQC.

Text from the source record.

Affected versions
  • Apache Camel PQC 4.19.0 before 4.20.0
  • Apache Camel PQC 4.18.0 before 4.18.2

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-40048

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Users are recommended to upgrade to version 4.20.0, which fixes the issue by replacing java.io.ObjectInputStream-based key and metadata storage with standard PKCS#8 (private key) / X.509 SubjectPublicKeyInfo (public key) Base64 JSON encoding.

CVE-2026-40048 in other vendors' advisories

Compare every advisory for CVE-2026-40048

Apache Software Foundation advisories, April 2026All Apache Software Foundation advisories

Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.

See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Messaging (ActiveMQ/Kafka/Pulsar)