PT-2026-55885 · Apache · Apache Camel
Andrea Cosentino
+1
·
Published
2026-07-06
·
Updated
2026-07-06
·
CVE-2026-43866
None
No severity ratings or metrics are available. When they are, we'll update the corresponding info on the page.
Name of the Vulnerable Software and Affected Versions
Apache Camel versions 3.0.0 through 4.14.7
Apache Camel versions 4.15.0 through 4.18.2
Apache Camel versions 4.19.0 through 4.20.9
Description
An issue exists in the Apache Camel JMS component where the
JmsBinding.extractBodyFromJms() function in camel-jms (and equivalent bindings in camel-sjms, camel-sjms2, camel-amqp, camel-activemq, and camel-activemq6) improperly handles the deserialization of incoming JMS ObjectMessage payloads when the mapJmsMessage option is enabled. Although a post-deserialization class check was implemented to restrict allowed classes, the org.apache.camel.support.DefaultExchangeHolder class is included in the allow-list. An attacker can send a crafted ObjectMessage with a DefaultExchangeHolder as the top-level object to bypass this check. The system then calls DefaultExchangeHolder.unmarshal(), allowing the attacker to inject arbitrary Exchange state—including message bodies, headers, properties, and variables—using only trusted java.lang and java.util types. This allows for the manipulation of routing, headers, exchange properties, and error handling without requiring a deserialization gadget chain.Recommendations
Upgrade to version 4.21.0.
Upgrade to version 4.14.8 for those on the 4.14.x LTS release stream.
Upgrade to version 4.18.3 for those on the 4.18.x release stream.
Restrict publish access to the queues and topics consumed by Camel to trusted producers via JMS broker authorization.
Avoid exposing JMS consumers that map ObjectMessage bodies to untrusted networks.
Deserialization of Untrusted Data
Found an issue in the description? Have something to add? Feel free to write us 👾
Weakness Enumeration
Related Identifiers
Affected Products
Apache Camel