CVE-2026-40860

CRITICALPre-NVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
9.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.8Exploit: None knownExposed: 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)
EG Risk
60(Track)
EG Risk 60/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
Severity98% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
67%
KEV
Not listed

Published

April 27, 2026

Last Modified

September 10, 2026

Advisory Details (7)

Auto-updated Sep 17, 2026
No patch confirmed yet.
generic

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

https://camel.apache.org/security/CVE-2026-40860.html
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-2026-40860 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

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

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(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatcamel-jms2026-06-02redhat

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

(6 across 1 ecosystem)
Maven(6)
PackageVulnerable rangeFixed inDependents
org.apache.camel:camel-activemq4.19.04.20.0—
org.apache.camel:camel-activemq64.19.04.20.0—
org.apache.camel:camel-amqp4.19.04.20.0—
org.apache.camel:camel-jms4.19.04.20.0—
org.apache.camel:camel-sjms4.19.04.20.0—
org.apache.camel:camel-sjms24.19.04.20.0—

Weakness Classification(1)

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

Data Freshness Timeline

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

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

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 September 10, 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 1% probability of exploitation in the next 30 days, which ranks it in the top 32.5% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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