CVE-2026-40859

HIGHPre-NVD 8.18.1—
EchelonGraph scoreMEDIUM confidence

Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-07-06. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 8.1; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.9%CVSS: 8.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.

CVSS v3
8.1
EG Score
8.1HIGHmedium confidence
EG Risk
37
EG Risk 37/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity81% × 45%
Exploitation1% × 40%
Automatability0% × 15%
EPSS PROB
0.9%
EPSS %ILE
57th
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
Patch available.
generic

oss-security - CVE-2026-40859: Apache Camel: Camel-Vertx-Http: Unsafe Java deserialization of HTTP response bodies via a raw ObjectInputStream when transferException is enabled

http://www.openwall.com/lists/oss-security/2026/07/05/3
generic

Apache Camel Security Advisory - CVE-2026-40859 - Apache Camel

https://camel.apache.org/security/CVE-2026-40859.html

Vendor Advisories for CVE-2026-40859(3)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatcamel-vertx-http2026-08-13redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(2 across 1 ecosystem)
Maven(2)
PackageVulnerable rangeFix by version rangeDependents
org.apache.camel:camel-netty-http4.19.0
  • 4.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.20.0: fixed in 4.20.0
—
org.apache.camel:camel-vertx-http4.19.0
  • 4.0.0 up to 4.14.8: fixed in 4.14.8
  • 4.15.0 up to 4.18.3: fixed in 4.18.3
  • 4.19.0 up to 4.20.0: fixed in 4.20.0
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 34× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 268 total refreshes for this CVE.

  1. 2026-10-03 14:25 UTCEPSS rescore
  2. 2026-10-01 19:50 UTCEPSS rescore
  3. 2026-09-30 15:03 UTCEPSS rescore
  4. 2026-09-27 13:48 UTCEPSS rescore
  5. 2026-09-26 15:58 UTCEPSS rescore
  6. 2026-09-23 17:53 UTCEPSS rescore
  7. 2026-09-23 06:26 UTCEG score recompute
  8. 2026-09-23 06:26 UTCVendor advisory
  9. 2026-09-20 20:15 UTCEPSS rescore
  10. 2026-09-18 19:28 UTCEPSS rescore
  11. 2026-09-18 06:05 UTCEG score recompute
  12. 2026-09-18 06:05 UTCVendor advisory
  13. 2026-09-17 19:31 UTCEPSS rescore
  14. 2026-09-16 14:08 UTCEPSS rescore
  15. 2026-09-16 05:15 UTCEPSS rescore
  16. 2026-09-15 03:11 UTCEPSS rescore
  17. 2026-09-13 23:57 UTCEG score recompute
  18. 2026-09-13 23:57 UTCVendor advisory
  19. 2026-09-13 16:47 UTCEPSS rescore
  20. 2026-09-13 08:45 UTCEG score recompute
  21. 2026-09-13 08:45 UTCVendor advisory
  22. 2026-09-12 15:01 UTCEPSS rescore
  23. 2026-09-12 13:39 UTCEG score recompute
  24. 2026-09-12 13:39 UTCVendor advisory
  25. 2026-09-11 14:53 UTCEPSS rescore
Show 75 more
  1. 2026-09-11 09:37 UTCEPSS rescore
  2. 2026-09-10 09:34 UTCEPSS rescore
  3. 2026-09-08 22:00 UTCEPSS rescore
  4. 2026-09-07 16:01 UTCEPSS rescore
  5. 2026-09-06 14:12 UTCEG score recompute
  6. 2026-09-06 14:12 UTCVendor advisory
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-05 23:14 UTCEG score recompute
  9. 2026-09-05 23:14 UTCVendor advisory
  10. 2026-09-04 05:06 UTCEPSS rescore
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:53 UTCEPSS rescore
  13. 2026-09-01 04:39 UTCEPSS rescore
  14. 2026-08-30 20:41 UTCEG score recompute
  15. 2026-08-30 20:41 UTCVendor advisory
  16. 2026-08-30 19:17 UTCEPSS rescore
  17. 2026-08-30 08:29 UTCEG score recompute
  18. 2026-08-30 08:29 UTCVendor advisory
  19. 2026-08-30 01:22 UTCEPSS rescore
  20. 2026-08-28 21:41 UTCEPSS rescore
  21. 2026-08-27 22:00 UTCEG score recompute
  22. 2026-08-27 22:00 UTCVendor advisory
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-27 02:22 UTCEG score recompute
  25. 2026-08-27 02:22 UTCVendor advisory
  26. 2026-08-26 14:46 UTCEPSS rescore
  27. 2026-08-26 13:57 UTCEG score recompute
  28. 2026-08-26 13:57 UTCVendor advisory
  29. 2026-08-26 13:57 UTCGHSA enrichment
  30. 2026-08-25 13:49 UTCEPSS rescore
  31. 2026-08-25 12:04 UTCVendor advisory
  32. 2026-08-25 12:03 UTCGHSA enrichment
  33. 2026-08-24 20:49 UTCEG score recompute
  34. 2026-08-24 20:49 UTCVendor advisory
  35. 2026-08-24 20:49 UTCGHSA enrichment
  36. 2026-08-24 06:45 UTCVendor advisory
  37. 2026-08-24 06:45 UTCGHSA enrichment
  38. 2026-08-23 18:32 UTCVendor advisory
  39. 2026-08-23 18:32 UTCGHSA enrichment
  40. 2026-08-23 06:20 UTCEG score recompute
  41. 2026-08-23 06:20 UTCVendor advisory
  42. 2026-08-23 06:20 UTCGHSA enrichment
  43. 2026-08-23 00:19 UTCEPSS rescore
  44. 2026-08-22 18:07 UTCVendor advisory
  45. 2026-08-22 18:07 UTCGHSA enrichment
  46. 2026-08-22 05:25 UTCEG score recompute
  47. 2026-08-22 05:25 UTCVendor advisory
  48. 2026-08-22 05:25 UTCGHSA enrichment
  49. 2026-08-21 23:49 UTCEPSS rescore
  50. 2026-08-21 17:13 UTCVendor advisory
  51. 2026-08-21 17:13 UTCGHSA enrichment
  52. 2026-08-21 04:23 UTCEG score recompute
  53. 2026-08-21 04:23 UTCVendor advisory
  54. 2026-08-21 04:23 UTCGHSA enrichment
  55. 2026-08-20 22:55 UTCEPSS rescore
  56. 2026-08-20 15:49 UTCVendor advisory
  57. 2026-08-20 15:49 UTCGHSA enrichment
  58. 2026-08-20 02:55 UTCEG score recompute
  59. 2026-08-20 02:55 UTCVendor advisory
  60. 2026-08-20 02:55 UTCGHSA enrichment
  61. 2026-08-19 17:03 UTCEPSS rescore
  62. 2026-08-19 09:18 UTCVendor advisory
  63. 2026-08-19 09:18 UTCGHSA enrichment
  64. 2026-08-18 20:50 UTCEG score recompute
  65. 2026-08-18 20:50 UTCVendor advisory
  66. 2026-08-18 20:49 UTCGHSA enrichment
  67. 2026-08-18 13:48 UTCEPSS rescore
  68. 2026-08-18 00:01 UTCEG score recompute
  69. 2026-08-18 00:01 UTCVendor advisory
  70. 2026-08-18 00:01 UTCGHSA enrichment
  71. 2026-08-17 13:47 UTCEPSS rescore
  72. 2026-08-17 11:48 UTCVendor advisory
  73. 2026-08-17 11:48 UTCGHSA enrichment
  74. 2026-08-16 23:29 UTCEG score recompute
  75. 2026-08-16 23:29 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Same product

2 shown

Maven:org.apache.camel:camel-vertx-http · Maven:org.apache.camel:camel-netty-http

Frequently asked(5)

What is CVE-2026-40859?
CVE-2026-40859 is a high vulnerability published on July 6, 2026. 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…
When was CVE-2026-40859 disclosed?
CVE-2026-40859 was first published on July 6, 2026, with the most recent update on July 7, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40859 actively exploited?
CVE-2026-40859 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.9% probability of exploitation in the next 30 days (57th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-40859?
CVE-2026-40859 has a CVSS v3.1 base score of 8.1 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-40859?
A fix for CVE-2026-40859 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-40859 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-40859

Explore →

Is Your Infrastructure Affected by CVE-2026-40859?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs