cve.bz

CVE-2026-40859 apache camel: Deserialization of Untrusted Data

8.1 highEPSS 0.9%Fix available

High (8.1) in apache camel. EPSS 0.9% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-vertx-http 4.14.8, 4.18.3, 4.20.0.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
0.9% (unchanged from 0.9% a week ago; 0.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 60th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-07-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-502 Deserialization of Untrusted Data
OWASP Top 10
A08:2025 Software or Data Integrity Failures
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-40859 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-40859?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-40859?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-40859 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-40859

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-40859](https://cve.bz/cve/badge/CVE-2026-40859.svg)](https://cve.bz/cve/CVE-2026-40859)

HTML:

<a href="https://cve.bz/cve/CVE-2026-40859"><img src="https://cve.bz/cve/badge/CVE-2026-40859.svg" alt="CVE-2026-40859"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.0.0 before 4.14.8
Apache Software Foundation Apache Camelfrom 4.15.0 before 4.18.3
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.20.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-6qw3-4796-5984Mavenorg.apache.camel:camel-vertx-http>=4.0.0 <4.14.84.14.8
GHSA-6qw3-4796-5984Mavenorg.apache.camel:camel-vertx-http>=4.15.0 <4.18.34.18.3
GHSA-6qw3-4796-5984Mavenorg.apache.camel:camel-vertx-http>=4.19.0 <4.20.04.20.0
GHSA-6qw3-4796-5984Mavenorg.apache.camel:camel-netty-http>=4.0.0 <4.14.84.14.8
GHSA-6qw3-4796-5984Mavenorg.apache.camel:camel-netty-http>=4.15.0 <4.18.34.18.3
GHSA-6qw3-4796-5984Mavenorg.apache.camel:camel-netty-http>=4.19.0 <4.20.04.20.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

This vulnerability is rated as Important because it allows for remote code execution in Apache Camel applications using the `camel-vertx-http` component. Exploitation requires a non-default configuration where `transferException=true` or `allowJavaSerializedObject=true` is enabled on the producer endpoint, in addition to an attacker controlling the backend service or performing a man-in-the-middle attack on an unencrypted connection.

Red Hat's mitigation

To mitigate this issue, avoid enabling `transferException=true` or `allowJavaSerializedObject=true` on Apache Camel `camel-vertx-http` producer endpoints that communicate with untrusted or network-reachable backend services. Ensure all producer connections utilize TLS (HTTPS) to prevent man-in-the-middle attacks. If enabling these options is necessary, configure a strict deserialization filter using the `-Djdk.serialFilter` JVM system property, for example: `-Djdk.serialFilter="java.**;org.apache.camel.**;!*"`. This will restrict the classes allowed during deserialization, limiting the potential impact.

ProductPackageStateAdvisory
Red Hat Build of Apache Camel 3.33.2.SP3org.apache.camel/camel-vertx-http:4.18.3.redhat-00001Fixed 2026-07-30RHSA-2026:48118
Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16camel-vertx-httpFixed 2026-08-13RHSA-2026:54622
Red Hat build of Apache Camel 4 for Quarkus 3camel-vertx-httpAffected
Red Hat JBoss Enterprise Application Platform Expansion Packcamel-vertx-httpNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-40859.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-40859 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-40859 — Apache Camel camel-netty-http / camel-vertx-http producer-side unsafe deserialization of HTTP response bodi…

Attack patterns (CAPEC)

  • CAPEC-586 Object Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON