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
Trending — 4 sources updated this week
8.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
37(Track)
EG Risk 37/100SSVC: Track

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%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
56%
KEV
Not listed

Published

July 6, 2026

Last Modified

July 7, 2026

Advisory Details (2)

Auto-updated Jul 7, 2026
No patch confirmed yet.
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 / EcosystemFixed in / 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.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 40× in last 7d / 146× 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 188 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

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 in the National Vulnerability Database 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 1% probability of exploitation in the next 30 days, which ranks it in the top 43.7% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40859, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs