CVE-2026-40860

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-04-27. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 0

A fix is available — apply it.

JmsBinding.extractBodyFromJms() in camel-jms, and the equivalent JmsBinding class in camel-sjms, deserialized the payload of incoming JMS ObjectMessage values via javax.jms.ObjectMessage.getObject() without applying any ObjectInputFilter, class allowlist or class denylist. Because this code path is reached whenever the mapJmsMessage option is enabled (the default) and Camel acts as a JMS consumer, an attacker able to publish a crafted ObjectMessage to a queue or topic consumed by a Camel application could achieve remote code execution when a deserialization gadget chain was present on the classpath. The same handling was reached transitively through camel-sjms2 (whose Sjms2Endpoint extends SjmsEndpoint) and through camel-amqp (whose AMQPJmsBinding extends JmsBinding), and by other JMS-family components built on JmsComponent such as camel-activemq and camel-activemq6.

This issue affects Apache Camel: from 3.0.0 before 4.14.7, from 4.15.0 before 4.18.2, 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.7. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
54.9%
KEV
Not listed

Published

April 27, 2026

Last Modified

June 30, 2026

Advisory Details (7)

Auto-updated Jul 12, 2026
Patch available. Sources: redhat.
redhat Patch Available
https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-40860.json
redhat Patch Available

2463172 – (CVE-2026-40860) CVE-2026-40860 Apache Camel: camel-jms: camel-sjms: camel-sjms2: camel-amqp: camel-activemq: camel-activemq6: Apache Camel: Remote Code Execution via deserialization of JMS ObjectMessage

https://bugzilla.redhat.com/show_bug.cgi?id=2463172
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-40860
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:22453
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:17668
generic

oss-security - CVE-2026-40860: Apache Camel: Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp

http://www.openwall.com/lists/oss-security/2026/04/26/10
generic

Apache Camel Security Advisory - CVE-2026-40860 - Apache Camel

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

Vendor Advisories for CVE-2026-40860(3)

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

Patch Availability(2)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2026-06-02redhat
redhatcamel-jms2026-05-14redhat

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 8× in last 7d / 58× 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 298 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-40860?
CVE-2026-40860 is a critical vulnerability published on April 27, 2026. JmsBinding.extractBodyFromJms() in camel-jms, and the equivalent JmsBinding class in camel-sjms, deserialized the payload of incoming JMS ObjectMessage values via javax.jms.ObjectMessage.getObject() without applying any ObjectInputFilter, class allowlist or class denylist. Because this code path is…
When was CVE-2026-40860 disclosed?
CVE-2026-40860 was first published in the National Vulnerability Database on April 27, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-40860 actively exploited?
CVE-2026-40860 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 54.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-40860?
CVE-2026-40860 has a CVSS v3.1 base score of 9.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-40860?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-40860, 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-40860

Explore →

Is Your Infrastructure Affected by CVE-2026-40860?

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

Start Free Scan →Browse All CVEs