CVE-2026-40860: CWE-502 Deserialization of Untrusted Data in Apache Software Foundation Apache Camel
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.
AI Analysis
Technical Summary
The vulnerability CVE-2026-40860 in Apache Camel involves the deserialization of untrusted data in JMS ObjectMessages. Specifically, the JmsBinding.extractBodyFromJms() method in camel-jms and equivalent classes in related JMS components deserialize incoming JMS ObjectMessage payloads using javax.jms.ObjectMessage.getObject() without applying any ObjectInputFilter or class allowlist/denylist. This unsafe deserialization occurs when the mapJmsMessage option is enabled (which is the default) and Camel acts as a JMS consumer. An attacker capable of sending a crafted ObjectMessage to a queue or topic consumed by a vulnerable Camel application can achieve remote code execution if a deserialization gadget chain exists on the classpath. The vulnerability affects Apache Camel versions 3.0.0 up to but not including 4.14.7, 4.15.0 up to but not including 4.18.2, and 4.19.0 up to but not including 4.20.0. The vendor recommends upgrading to 4.14.7, 4.18.2, or 4.20.0 to remediate this issue. Red Hat advisories classify this as an important security update and provide patches in their builds.
Potential Impact
Successful exploitation of this vulnerability allows an unauthenticated remote attacker to execute arbitrary code on the system running the vulnerable Apache Camel application by sending a crafted JMS ObjectMessage. This can lead to full compromise of the affected system, including confidentiality, integrity, and availability impacts. The CVSS v3.1 base score is 9.8 (Critical), reflecting network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix is available. Users should upgrade to Apache Camel version 4.20.0 or later. For those on the 4.14.x LTS stream, upgrade to 4.14.7; for those on the 4.18.x stream, upgrade to 4.18.2. Red Hat provides patched builds addressing this vulnerability. Applying these updates will remediate the unsafe deserialization issue. No alternative mitigations are specified in the vendor advisory. Users should ensure that the mapJmsMessage option is carefully configured and consider disabling JMS ObjectMessage deserialization if upgrading is not immediately possible, although this is not explicitly stated in the advisory.
CVE-2026-40860: CWE-502 Deserialization of Untrusted Data in Apache Software Foundation Apache Camel
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.
CVSS v3.1
Score 9.8critical
Affected software
pkg:maven/org.apache.camel/camel-coreRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-40860 in Apache Camel involves the deserialization of untrusted data in JMS ObjectMessages. Specifically, the JmsBinding.extractBodyFromJms() method in camel-jms and equivalent classes in related JMS components deserialize incoming JMS ObjectMessage payloads using javax.jms.ObjectMessage.getObject() without applying any ObjectInputFilter or class allowlist/denylist. This unsafe deserialization occurs when the mapJmsMessage option is enabled (which is the default) and Camel acts as a JMS consumer. An attacker capable of sending a crafted ObjectMessage to a queue or topic consumed by a vulnerable Camel application can achieve remote code execution if a deserialization gadget chain exists on the classpath. The vulnerability affects Apache Camel versions 3.0.0 up to but not including 4.14.7, 4.15.0 up to but not including 4.18.2, and 4.19.0 up to but not including 4.20.0. The vendor recommends upgrading to 4.14.7, 4.18.2, or 4.20.0 to remediate this issue. Red Hat advisories classify this as an important security update and provide patches in their builds.
Potential Impact
Successful exploitation of this vulnerability allows an unauthenticated remote attacker to execute arbitrary code on the system running the vulnerable Apache Camel application by sending a crafted JMS ObjectMessage. This can lead to full compromise of the affected system, including confidentiality, integrity, and availability impacts. The CVSS v3.1 base score is 9.8 (Critical), reflecting network attack vector, no required privileges or user interaction, and high impact on confidentiality, integrity, and availability.
Mitigation Recommendations
A fix is available. Users should upgrade to Apache Camel version 4.20.0 or later. For those on the 4.14.x LTS stream, upgrade to 4.14.7; for those on the 4.18.x stream, upgrade to 4.18.2. Red Hat provides patched builds addressing this vulnerability. Applying these updates will remediate the unsafe deserialization issue. No alternative mitigations are specified in the vendor advisory. Users should ensure that the mapJmsMessage option is carefully configured and consider disabling JMS ObjectMessage deserialization if upgrading is not immediately possible, although this is not explicitly stated in the advisory.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-04-15T12:44:39.673Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-40860","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:22453","vendor":"Red Hat"},{"url":"https://access.redhat.com/errata/RHSA-2026:17668","vendor":"Red Hat"}]
Threat ID: 69ef291bba26a39fba10e184
Added to database: 04/27/2026, 09:15:07 UTC
Last enriched: 07/15/2026, 08:12:32 UTC
Last updated: 07/31/2026, 19:22:58 UTC
Views: 179
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.