Apache Software Foundation Apache Camel
Apache Camel, Apache Camel: Camel JMS - CVE-2026-40860 fix bypass via DefaultExchangeHolder
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.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 3.0.0, < 4.14.8
- >= 4.15.0, < 4.18.3
- >= 4.19.0, < 4.21.0
Fixed in 4.14.8, 4.18.3, 4.21.0
- >= 3.0.0, < 4.14.8
- >= 4.15.0, < 4.18.3
- >= 4.19.0, < 4.21.0
Fixed in 4.14.8, 4.18.3, 4.21.0
Mitigation
Upgrade Apache Camel to 4.14.8 or 4.18.3 or 4.21.0 or later.
Upgrade Apache Camel to 4.14.8 or 4.18.3 or 4.21.0 or later.
References
- Vendor advisory camel.apache.org/security/CVE-2026-43866.html
Timeline
Days relative to CVE publicationFirst public PoC 6.2 days after publication; not in CISA KEV. First PoC: oscerd/CVE-2026-43866 (created 12 Jul 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| oscerd/CVE-2026-43866 | 12 Jul 2026 +6.2 d | 0 | PoC |
Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.
PoC characteristics
What to hunt for in your logs · from 1 PoC repoGET /exploit/attack
- Ports
- 8080
- Seen in
- 1 repo: oscerd/CVE-2026-43866
- Evidence
- oscerd/CVE-2026-43866/README.md:107
Regex
Generated from PoC characteristics; not yet reviewed. Matches the request path and query.
(?i)^/exploit/attack(?:[?#].*)?$
Suricata
Template generated from PoC characteristics. Review before deploying.
alert http any any -> $HOME_NET [8080] (msg:"GG PoC-Monitor CVE-2026-43866 Apache Software Foundation Apache Camel exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/exploit/attack"; reference:url,poc.griffinguard.io/cve/CVE-2026-43866; classtype:web-application-attack; sid:9051075; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: Apache Software Foundation Apache Camel exploit attempt (CVE-2026-43866)
id: gg-pocmon-cve-2026-43866-9051075
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-43866. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-43866
logsource:
category: webserver
detection:
selection:
cs-method: GET
cs-uri-stem|contains|all:
- '/exploit/attack'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: high
tags:
- attack.initial_access
- attack.t1190
- cve.2026.43866