CVE-2026-43866 and CVE-2026-40860: Deserialization of Untrusted Data vulnerability in Apache Camel, Apache Camel JMS component
This Apache advisory covers CVE-2026-43866 and CVE-2026-40860 in Apache Camel JMS. Its rating, versions and guidance apply to the bulletin as a whole, not to each of its 2 CVEs.
Key facts
- Bulletin rating
- High, CVSS 7.3
- Affected
- 3.0.0 through 4.14.8; 4.15.0 through 4.18.3; 4.19.0 through 4.21.0 and 1 more below
- Fixed in
- 4.21.0, 4.14.8, 4.18.3
- Source published
- Source revised
- Listed by VulniPulse
Compiled by VulniPulse from the linked sources. How records are collected and checked.
Affected products & platforms
Description
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.
Text from the source record.
- 3.0.0 through 4.14.8
- 4.15.0 through 4.18.3
- 4.19.0 through 4.21.0
- 4.19.0 through 4.21.0.
Official advisory · high-confidence parse· fetched ·verify at source
Fix and mitigation
Upgrade to the first fixed release for your version, shown in the table above.
Vendor guidance
- Users are recommended to upgrade to version 4.21.0, which fixes the issue.
Workarounds
- 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.
More Apache Software Foundation advisories
CVE-2026-96295Nov 20, 2026Apache Texera: Authenticated users can bypass normal controls on the reading and writingCVE-2026-121649Nov 19, 2026Apache Tomcat information disclosureCVE-2026-133325Nov 19, 2026Key exchange without entity authentication vulnerability in Apache TomcatCVE-2026-118436Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118233Nov 19, 2026Apache Tomcat denial of serviceCVE-2026-118028Nov 19, 2026Execution After Redirect (EAR) vulnerability in Apache Tomcat in RedirectValve
Apache Software Foundation advisories, July 2026All Apache Software Foundation advisories
Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.
See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.