Apache Camel-Vertx-Http and Camel-Netty-Http: Unsafe Java deserialization of HTTP response bodies via a raw ObjectInputStream when transferException is enabled

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

8.1 · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

EPSS

• CVE-2026-40859: 0.89% estimated exploitation activity in the next 30 days; percentile 59.33 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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…

Published by the source

6 Jul 2026, 09:30 UTC

Last modified by the source

26 Aug 2026, 15:17 UTC

Source last checked

26 Oct 2026, 16:55 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6qw3-4796-5984

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-40859

Advisory: Apache Camel-Vertx-Http and Camel-Netty-Http: Unsafe Java deserialization of HTTP response bodies via a raw ObjectInputStream when transferException is enabled
IDs: CVE-2026-40859, GHSA-6qw3-4796-5984
Record: https://patchnext.com/advisories/cve-2026-40859 (revision 1, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-vertx-http 4.20.0, 4.18.3, 4.14.8; org.apache.camel:camel-netty-http 4.20.0, 4.18.3, 4.14.8. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-vertx-http: affected >= 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
- Maven org.apache.camel:camel-netty-http: affected >= 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

## Suggested inspection (read-only)
- Maven org.apache.camel:camel-vertx-http: check the installed version with your package manager.
- Maven org.apache.camel:camel-netty-http: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.camel:camel-vertx-http, org.apache.camel:camel-netty-http.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6qw3-4796-5984 (GitHub-reviewed advisory GHSA-6qw3-4796-5984 lists affected ranges: Maven org.apache.camel:camel-vertx-http >=4.0.0 =4.15.0 =4.19.0 =4.0.0 =4.15.0 =4.19.0 <4.20.0)

Commands are suggestions: review each one before running it.