# CVE-2026-40859: Apache Camel-Vertx-Http and Camel-Netty-Http: Unsafe Java deserialization of HTTP response bodies via a raw ObjectInputStream when transferException is enabled > Attackers can achieve remote code execution via unsafe Java deserialization of HTTP responses when transferException is enabled in Apache Camel. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jul 2026 - **Updated:** 6 Jul 2026 - **Also known as:** GHSA-6qw3-4796-5984 ## What is CVE-2026-40859? CVE-2026-40859 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-502 (Deserialization of Untrusted Data) ## Which versions are affected by CVE-2026-40859? 12 open source packages ship an affected version, including org.apache.camel:camel-netty-http and org.apache.camel:camel-vertx-http. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-netty-http` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-netty-http` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-netty-http` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-netty-http` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-netty-http` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-netty-http` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-vertx-http` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-vertx-http` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-vertx-http` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-vertx-http` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-vertx-http` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-vertx-http` | Maven | From 4.19.0 | 4.20.0 | Products: Apache Camel. ## How do I fix CVE-2026-40859? Upgrade org.apache.camel:camel-netty-http to a fixed version for your release line: 4.14.8, 4.18.3 or 4.20.0. ## Is CVE-2026-40859 being exploited? There is no known exploitation of CVE-2026-40859 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-40859 — Apache Camel camel-netty-http / camel-vertx-http producer-side unsafe deserialization of HTTP response bodies (RCE) (github_poc): https://github.com/oscerd/CVE-2026-40859 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-40859 and fix it if it is affected. What it is: CVE-2026-40859 is a high-severity unsafe deserialization vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-40859 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-netty-http (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-netty-http (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-netty-http (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-netty-http (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-netty-http (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-netty-http (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-vertx-http (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-vertx-http (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-vertx-http (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-vertx-http (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-vertx-http (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-vertx-http (Maven): affected from 4.19.0; fixed in 4.20.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-40859/ (Markdown: https://insights.sbomify.com/CVE-2026-40859/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40859 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40859 - OSV: https://osv.dev/vulnerability/CVE-2026-40859 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-40859/ Summaries are generated and may contain mistakes; the official description above is the record.