CVSS 3.1
8.1 highCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HHigh (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.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:Horg.apache.camel:camel-vertx-http (Maven): fixed in 4.14.8, 4.18.3, 4.20.0org.apache.camel:camel-netty-http (Maven): fixed in 4.14.8, 4.18.3, 4.20.0Explain 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.
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Apache Software Foundation Apache Camel | from 4.0.0 before 4.14.8 |
| Apache Software Foundation Apache Camel | from 4.15.0 before 4.18.3 |
| Apache Software Foundation Apache Camel | from 4.19.0 before 4.20.0 |
| Advisory | Ecosystem | Package | Affected | Fixed in |
|---|---|---|---|---|
| GHSA-6qw3-4796-5984 | Maven | org.apache.camel:camel-vertx-http | >=4.0.0 <4.14.8 | 4.14.8 |
| GHSA-6qw3-4796-5984 | Maven | org.apache.camel:camel-vertx-http | >=4.15.0 <4.18.3 | 4.18.3 |
| GHSA-6qw3-4796-5984 | Maven | org.apache.camel:camel-vertx-http | >=4.19.0 <4.20.0 | 4.20.0 |
| GHSA-6qw3-4796-5984 | Maven | org.apache.camel:camel-netty-http | >=4.0.0 <4.14.8 | 4.14.8 |
| GHSA-6qw3-4796-5984 | Maven | org.apache.camel:camel-netty-http | >=4.15.0 <4.18.3 | 4.18.3 |
| GHSA-6qw3-4796-5984 | Maven | org.apache.camel:camel-netty-http | >=4.19.0 <4.20.0 | 4.20.0 |
Red Hat rates this Important.
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.
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.
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Build of Apache Camel 3.33.2.SP3 | org.apache.camel/camel-vertx-http:4.18.3.redhat-00001 | Fixed 2026-07-30 | RHSA-2026:48118 |
| Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16 | camel-vertx-http | Fixed 2026-08-13 | RHSA-2026:54622 |
| Red Hat build of Apache Camel 4 for Quarkus 3 | camel-vertx-http | Affected | |
| Red Hat JBoss Enterprise Application Platform Expansion Pack | camel-vertx-http | Not 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.
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.
The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.