Widely used integration framework; RCE in JMS path could disrupt enterprise apps.
CVE-2026-40860
Apache Camel JMS deserialization RCE via ObjectMessage when mapJmsMessage is enabled.
Is CVE-2026-40860 being exploited?
Not confirmed. CVE-2026-40860 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 1.2% probability of exploitation in the next 30 days.
How severe is CVE-2026-40860?
CVE-2026-40860 is rated Critical with a CVSS score of 9.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-40860?
Yes. A fix has been recorded for CVE-2026-40860. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-40860 affect?
CVE-2026-40860 affects Apache Camel (JMS/SJMS/AMQP bindings) affected: 3.0.0–4.14.7, 4.15.0–4.18.2, 4.19.0–4.20.0. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-40860?
Upgrade to Camel 4.20.0+ (or 4.14.7/4.18.2 for LTS streams).
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote code execution via crafted JMS ObjectMessage; attacker can execute code on the Camel consumer host.
Patch when possible
- affected>= 3.0.0 and < 4.14.7
- affected>= 4.15.0 and < 4.18.2
- affected>= 4.19.0 and < 4.20.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.