Summary
Apache camel-jms, camel-sjms, camel-sjms2 and camel-amqp: Unsafe Deserialization of JMS ObjectMessage
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.
Impact
Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect. Typical impact: arbitrary code execution or logic abuse.
CVE-2026-40860 has a CVSS score of 9.8 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.14.7, 4.18.2, 4.20.0); upgrading removes the vulnerable code path.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
org.apache.camel:camel-jms to 4.14.7 or later; org.apache.camel:camel-jms to 4.18.2 or later; org.apache.camel:camel-jms to 4.20.0 or later; org.apache.camel:camel-sjms to 4.14.7 or later; org.apache.camel:camel-sjms to 4.18.2 or later; org.apache.camel:camel-sjms to 4.20.0 or later; org.apache.camel:camel-sjms2 to 4.14.7 or later; org.apache.camel:camel-sjms2 to 4.18.2 or later; org.apache.camel:camel-sjms2 to 4.20.0 or later; org.apache.camel:camel-amqp to 4.14.7 or later; org.apache.camel:camel-amqp to 4.18.2 or later; org.apache.camel:camel-amqp to 4.20.0 or later; org.apache.camel:camel-activemq to 4.14.7 or later; org.apache.camel:camel-activemq to 4.18.2 or later; org.apache.camel:camel-activemq to 4.20.0 or later; org.apache.camel:camel-activemq6 to 4.14.7 or later; org.apache.camel:camel-activemq6 to 4.18.2 or later; org.apache.camel:camel-activemq6 to 4.20.0 or later
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-40860? CVE-2026-40860 is a critical-severity insecure deserialization vulnerability in org.apache.camel:camel-jms (maven), affecting versions >= 3.0.0, < 4.14.7. It is fixed in 4.14.7, 4.18.2, 4.20.0. Untrusted serialized data is processed by a deserializer that can instantiate arbitrary objects or execute code as a side effect.
- How severe is CVE-2026-40860? CVE-2026-40860 has a CVSS score of 9.8 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
- Which packages are affected by CVE-2026-40860?
org.apache.camel:camel-jms(maven) (versions >= 3.0.0, < 4.14.7)org.apache.camel:camel-sjms(maven) (versions >= 3.0.0, < 4.14.7)org.apache.camel:camel-sjms2(maven) (versions >= 3.0.0, < 4.14.7)org.apache.camel:camel-amqp(maven) (versions >= 3.0.0, < 4.14.7)org.apache.camel:camel-activemq(maven) (versions >= 3.0.0, < 4.14.7)org.apache.camel:camel-activemq6(maven) (versions >= 3.0.0, < 4.14.7)
- Is there a fix for CVE-2026-40860? Yes. CVE-2026-40860 is fixed in 4.14.7, 4.18.2, 4.20.0. Upgrade to this version or later.
- Is CVE-2026-40860 exploitable, and should I be worried? Whether CVE-2026-40860 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-40860 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-40860?
- Upgrade
org.apache.camel:camel-jmsto 4.14.7 or later - Upgrade
org.apache.camel:camel-jmsto 4.18.2 or later - Upgrade
org.apache.camel:camel-jmsto 4.20.0 or later - Upgrade
org.apache.camel:camel-sjmsto 4.14.7 or later - Upgrade
org.apache.camel:camel-sjmsto 4.18.2 or later - Upgrade
org.apache.camel:camel-sjmsto 4.20.0 or later - Upgrade
org.apache.camel:camel-sjms2to 4.14.7 or later - Upgrade
org.apache.camel:camel-sjms2to 4.18.2 or later - Upgrade
org.apache.camel:camel-sjms2to 4.20.0 or later - Upgrade
org.apache.camel:camel-amqpto 4.14.7 or later - Upgrade
org.apache.camel:camel-amqpto 4.18.2 or later - Upgrade
org.apache.camel:camel-amqpto 4.20.0 or later - Upgrade
org.apache.camel:camel-activemqto 4.14.7 or later - Upgrade
org.apache.camel:camel-activemqto 4.18.2 or later - Upgrade
org.apache.camel:camel-activemqto 4.20.0 or later - Upgrade
org.apache.camel:camel-activemq6to 4.14.7 or later - Upgrade
org.apache.camel:camel-activemq6to 4.18.2 or later - Upgrade
org.apache.camel:camel-activemq6to 4.20.0 or later
- Upgrade