CVE-2026-40860 is a critical-severity (CVSS 9.8) Deserialization of Untrusted Data vulnerability in org.apache.camel:camel-jms. A fix is available for org.apache.camel:camel-jms — see the affected versions and patch details below.
Apache Camel: Unsafe Deserialization of JMS ObjectMessage in camel-jms, camel-sjms, camel-sjms2 and camel-amqp
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- A successful exploit gives an attacker total control of the affected component, not partial access.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-40860.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-40860 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.camel:camel-jms☕org.apache.camel:camel-jms☕org.apache.camel:camel-jms☕org.apache.camel:camel-sjms☕org.apache.camel:camel-sjms☕org.apache.camel:camel-sjms☕org.apache.camel:camel-sjms2☕org.apache.camel:camel-sjms2+10 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
Description
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.camel:camel-jms | ≥ 3.0.0&&< 4.14.7 | 4.14.7org.apache.camel:camel-jms:4.14.7 |
| ☕Maven | org.apache.camel:camel-jms | ≥ 4.15.0&&< 4.18.2 | 4.18.2org.apache.camel:camel-jms:4.18.2 |
| ☕Maven | org.apache.camel:camel-jms | ≥ 4.19.0&&< 4.20.0 | 4.20.0org.apache.camel:camel-jms:4.20.0 |
| ☕Maven | org.apache.camel:camel-sjms | ≥ 3.0.0&&< 4.14.7 | 4.14.7org.apache.camel:camel-sjms:4.14.7 |
| ☕Maven | org.apache.camel:camel-sjms | ≥ 4.15.0&&< 4.18.2 | 4.18.2org.apache.camel:camel-sjms:4.18.2 |
| ☕Maven | org.apache.camel:camel-sjms | ≥ 4.19.0&&< 4.20.0 | 4.20.0org.apache.camel:camel-sjms:4.20.0 |
Affected Products
camelapacheDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-jms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-jms to 4.14.7 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-40860 is resolved across your whole dependency graph.
Workarounds
Do not deserialise data from untrusted sources: where the format allows it, restrict deserialisation to an explicit allowlist of expected types, and prefer a data-only format (JSON, Protobuf) over one that can reconstruct arbitrary objects until you can upgrade.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat build of Apache Camel 4.18.1 for Spring Boot 3.5.14 | camel-amqp | RHSA-2026:17668 |
Frequently Asked Questions
Is CVE-2026-40860 in your dependencies?
Find it across Maven, including transitive dependencies.