Skip to main content
VulnerabilityPublished

CVE-2026-40859: Apache Camel · Deserialization of Untrusted Data

Affects Apache CamelSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.1 High · fixed in 4.20.0 : patch Apache Camel soon.

Data as of 18 Nov 2026, 20:25 UTC

CVSS 3.1 base score
8.1High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.8% chance of exploitation in 30 days – higher than 59% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.20.0, 4.18.3, 4.14.8
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.

What to do

Upgrade Apache to 4.20.0, 4.18.3 or 4.14.8.

Affected software

ProductAffectedFixed in
Apache Software FoundationApache CamelAffected
  • >=4.19.0 <4.20.0
Fixed in
  • 4.20.0
Apache Software FoundationApache CamelAffected
  • >=4.15.0 <4.18.3
Fixed in
  • 4.18.3
Apache Software FoundationApache CamelAffected
  • >=4.0.0 <4.14.8
Fixed in
  • 4.14.8
MavenApache Software Foundation/org.apache.camel:camel-vertx-httppkg:maven/Apache Software Foundation/org.apache.camel:camel-vertx-httpOther threatsAffected
  • >=4.0.0 <4.14.8
  • >=4.15.0 <4.18.3
  • >=4.19.0 <4.20.0
Fixed in
  • 4.14.8
  • 4.18.3
  • 4.20.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available in Apache Camel versions 4.14.8, 4.18.3, and 4.20.0. Users should upgrade to one of these versions depending on their release stream. After upgrading, deserialization is restricted by a default ObjectInputFilter, which can be customized. For users unable to upgrade immediately, do not enable transferException=true or allowJavaSerializedObject=true on producers communicating with untrusted or network-exposed backends. Ensure producer connections use TLS (HTTPS) to prevent man-in-the-middle attacks. Additionally, set an explicit JVM deserialization filter (-Djdk.serialFilter) to constrain deserialization to safe classes.

Description

Deserialization of Untrusted Data vulnerability in Apache Camel. The camel-vertx-http component deserializes HTTP response bodies carrying the Content-Type application/x-java-serialized-object using a raw java.io.ObjectInputStream, without applying any ObjectInputFilter (VertxHttpHelper.deserializeJavaObjectFromStream) This deserialization path is reached only when the producer endpoint is configured with transferException=true (or the component-level allowJavaSerializedObject=true) and throwExceptionOnFailure is left at its default value of true; in that case a backend HTTP response with a 5xx status and the application/x-java-serialized-object content type has its body deserialized with no class restrictions. An attacker who controls the backend the Camel producer talks to - through a man-in-the-middle position on an unencrypted (plain HTTP) connection, or by compromising the backend service - can return a crafted serialized Java object and, if a suitable gadget chain is present on the classpath, achieve remote code execution on the Camel application host. The path is not reachable in the default configuration, where transferException is false. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.20.0. Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, the deserialization performed by both helper utilities is constrained by a default ObjectInputFilter (allow-list java.**;javax.**;org.apache.camel.**;!*), which can be customised through the new deserializationFilter endpoint option or the JVM-wide -Djdk.serialFilter system property. For deployments that cannot upgrade immediately: do not enable transferException=true (or allowJavaSerializedObject=true) on producers that talk to untrusted or network-reachable backends; ensure producer connections use TLS (https) so that a response cannot be substituted by a man-in-the-middle; and, where the option is required, set an explicit -Djdk.serialFilter allow-list (for example java.**;org.apache.camel.**;!*) to constrain deserialization.

References

Community reviews

Loading reviews…