{"id":"CVE-2026-40048","summary":"Apache Camel PQC: Unsafe Deserialization from FileBasedKeyLifecycleManager","details":"The Camel-PQC FileBasedKeyLifecycleManager class deserializes the contents of `\u003ckeyId\u003e.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.\n\nThis issue affects Apache Camel: from 4.19.0 before 4.20.0, from 4.18.0 before 4.18.2.\n\nUsers 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.","aliases":["GHSA-v3vg-332r-mw99"],"modified":"2026-07-08T08:13:12.568111791Z","published":"2026-04-27T07:53:54.636Z","database_specific":{"cwe_ids":["CWE-502"],"unresolved_ranges":[{"extracted_events":[{"introduced":"4.19.0"},{"fixed":"4.20.0"},{"introduced":"4.18.0"},{"fixed":"4.18.2"}],"source":"AFFECTED_FIELD"},{"extracted_events":[{"introduced":"4.19.0"},{"fixed":"4.20.0"},{"introduced":"4.18.0"},{"fixed":"4.18.2"}],"source":"DESCRIPTION"}],"cna_assigner":"apache","osv_generated_from":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/40xxx/CVE-2026-40048.json"},"references":[{"type":"WEB","url":"http://www.openwall.com/lists/oss-security/2026/04/26/6"},{"type":"WEB","url":"https://repo.maven.apache.org/maven2"},{"type":"WEB","url":"https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40048.json"},{"type":"ADVISORY","url":"https://access.redhat.com/security/cve/CVE-2026-40048"},{"type":"ADVISORY","url":"https://camel.apache.org/security/CVE-2026-40048.html"},{"type":"ADVISORY","url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/40xxx/CVE-2026-40048.json"},{"type":"ADVISORY","url":"https://nvd.nist.gov/vuln/detail/CVE-2026-40048"},{"type":"REPORT","url":"https://bugzilla.redhat.com/show_bug.cgi?id=2463176"}],"affected":[{"ranges":[{"type":"GIT","repo":"https://github.com/apache/camel","events":[{"introduced":"dd22f752e240bd1343af15c775ef02d754f6df38"},{"fixed":"2326a42c5595aa1eee21caafeee75f8e7f0261ea"},{"introduced":"3e9f3011ad48de66fef582ade9794c7340c23af7"}],"database_specific":{"extracted_events":[{"introduced":"4.18.0"},{"fixed":"4.18.2"},{"introduced":"4.19.0"},{"last_affected":"4.19.0"}],"source":["CPE_RANGE","CPE_STRING"],"cpe":["cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*","cpe:2.3:a:apache:camel:4.19.0:*:*:*:*:*:*:*"]}}],"versions":["4.19.0"],"database_specific":{"source":"https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2026-40048.json"}}],"schema_version":"1.7.5","severity":[{"type":"CVSS_V3","score":"CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H"}]}