CVE-2026-40860
CriticalCVSS 9.8Exploitation Probability (EPSS)
Elevated risk55th percentile — higher than 55% of all known CVEs
Summary
A vulnerability in Apache Camel allows remote code execution via deserialization of untrusted data from JMS ObjectMessage. The JmsBinding.extractBodyFromJms() function does not apply deserialization filters, enabling an attacker to publish a crafted message to a queue or topic consumed by a Camel application.
Risk Assessment
An attacker can remotely execute arbitrary code on the server if a suitable deserialization gadget is present on the classpath, leading to full system compromise, data theft, or service disruption.
Recommendation
Immediately upgrade Apache Camel to version 4.20.0, or to 4.14.7 for the 4.14.x LTS branch, or to 4.18.2 for the 4.18.x branch. As a workaround, disable the mapJmsMessage option or apply an ObjectInputFilter.
Original NVD description (English source)
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.