Apache Camel, Apache Camel: Camel JMS - CVE-2026-40860 fix bypass via DefaultExchangeHolder
- Published
- Last modified
- Where the record stands: published, rejected by its publisher, or superseded by another id.What do these mean? →
- published
- Whether CISA lists it in its Known Exploited Vulnerabilities catalog: proof that attackers are using it.What do these mean? →
- Not listed in CISA KEV
- Fix
- Fixed in 4.14.8, 4.18.3, 4.21.0
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- 1 proof of concept on GitHub
- Exploitation: none
- Automatable: yes
- Technical impact: partial
Summary
Deserialization of Untrusted Data vulnerability in Apache Camel, Apache Camel JMS component. JmsBinding.extractBodyFromJms() in camel-jms - and the equivalent JmsBinding in camel-sjms - deserializes the payload of an incoming JMS ObjectMessage via jakarta.jms.ObjectMessage.getObject() whenever the mapJmsMessage option is enabled (the default) and Camel acts as a JMS consumer. The CVE-2026-40860 hardening added a post-deserialization class check that rejects classes outside the default allow-list java.;javax.;org.apache.camel.**;!*. However org.apache.camel.support.DefaultExchangeHolder itself lives in the allow-listed org.apache.camel.** namespace, so an ObjectMessage whose top-level object is a DefaultExchangeHolder passes the check. The receiving side then calls DefaultExchangeHolder.unmarshal() on it without requiring the transferExchange option to be enabled - an asymmetric trust boundary, since the sending side gates ObjectMessage and transferExchange handling but the receiving side did not - writing every non-null field of the holder into the Exchange: the message body, the IN and OUT headers, the exchange properties, the variables, the exchange id and the exception. An attacker who can publish an ObjectMessage to a queue or topic consumed by an affected Camel application can therefore inject arbitrary Exchange state using only universally-trusted java.lang and java.util types, with no deserialization gadget chain required, to manipulate routing and headers, exchange properties and error handling. The same handling applies to camel-sjms and camel-sjms2, and to the JMS-family components built on JmsComponent and JmsBinding: camel-amqp, camel-activemq and camel-activemq6. This is a bypass of the CVE-2026-40860 fix rather than a flaw in it. This issue affects Apache Camel: from 3.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0; Apache Camel: from 3.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.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.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, JMS ObjectMessage handling is disabled by default in camel-jms, camel-sjms and the JMS-family components (a new objectMessageEnabled option defaults to false at the component and endpoint level), so an incoming ObjectMessage - including a DefaultExchangeHolder payload - is no longer deserialized unless the option is explicitly enabled; only set objectMessageEnabled=true when the consumed JMS destination is fed exclusively by trusted producers. For deployments that cannot upgrade immediately, restrict publish access to the queues and topics consumed by Camel to trusted producers via JMS broker authorization, and do not expose JMS consumers that map ObjectMessage bodies to untrusted networks; a JMS-provider deserialization allow-list does not mitigate this specific bypass because the crafted payload uses only universally-trusted classes.
Timeline
- CVE published
- CISA SSVC assessment
Exploitation: none · Automatable: yes · Technical impact: partial
- Record last updated
Affected versions
- org.apache.camel:camel-jms
From 3.0.0 · fixed in 4.14.8; From 4.15.0 · fixed in 4.18.3; From 4.19.0 · fixed in 4.21.0
- org.apache.camel:camel-sjms
From 3.0.0 · fixed in 4.14.8; From 4.15.0 · fixed in 4.18.3; From 4.19.0 · fixed in 4.21.0
- org.apache.camel:camel-jmsMaven
From 3.0.0 · fixed in 4.14.8
- org.apache.camel:camel-jmsMaven
From 4.15.0 · fixed in 4.18.3
- org.apache.camel:camel-jmsMaven
From 4.19.0 · fixed in 4.21.0
- org.apache.camel:camel-sjmsMaven
From 3.0.0 · fixed in 4.14.8
- org.apache.camel:camel-sjmsMaven
From 4.15.0 · fixed in 4.18.3
- org.apache.camel:camel-sjmsMaven
From 4.19.0 · fixed in 4.21.0
- org.apache.camel:camel-sjms2Maven
From 3.0.0 · fixed in 4.14.8
- org.apache.camel:camel-sjms2Maven
From 4.15.0 · fixed in 4.18.3
- org.apache.camel:camel-sjms2Maven
From 4.19.0 · fixed in 4.21.0
- org.apache.camel:camel-amqpMaven
From 3.0.0 · fixed in 4.14.8
- org.apache.camel:camel-amqpMaven
From 4.15.0 · fixed in 4.18.3
- org.apache.camel:camel-amqpMaven
From 4.19.0 · fixed in 4.21.0
- org.apache.camel:camel-activemqMaven
From 3.0.0 · fixed in 4.14.8
- org.apache.camel:camel-activemqMaven
From 4.15.0 · fixed in 4.18.3
- org.apache.camel:camel-activemqMaven
From 4.19.0 · fixed in 4.21.0
- org.apache.camel:camel-activemq6Maven
From 3.0.0 · fixed in 4.14.8
- org.apache.camel:camel-activemq6Maven
From 4.15.0 · fixed in 4.18.3
- org.apache.camel:camel-activemq6Maven
From 4.19.0 · fixed in 4.21.0