CVE-2026-46454
Published:July 06, 2026
Updated:August 04, 2026
Improper Input Validation vulnerability in Apache Camel Cometd Component.
The camel-cometd component maps inbound Bayeux (CometD) message headers into the Camel Exchange without applying a HeaderFilterStrategy. CometdBinding.populateExchangeFromMessage copies the entire ext.CamelHeaders map supplied by the CometD client directly onto the Camel message (message.setHeaders), so any header name - including Camel-internal control headers such as CamelHttpUri, CamelFileName or CamelJmsDestinationName - is accepted unmodified. Because a CometdComponent installs no Bayeux SecurityPolicy by default, any client that can complete the Bayeux handshake against the CometD endpoint can publish such a message without authentication. An attacker can therefore inject arbitrary Camel control headers that influence the behaviour of downstream producers in the route (for example redirecting an HTTP producer, changing a file name, or overriding a JMS destination); the injected headers also persist across internal direct, seda and vm hops. The concrete downstream impact depends on which producers the route uses.
This issue affects Apache Camel: from 4.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. The fix implements a HeaderFilterStrategy in the camel-cometd binding (a long-standing TODO in the code) that filters the Camel header namespace case-insensitively on inbound mapping, so client-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from inbound CometD messages before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), and install an explicit Bayeux SecurityPolicy on the CometdComponent so that only authenticated clients can publish.
Affected Packages
https://github.com/apache/camel.git (GITHUB):
Affected version(s) >=camel-4.15.0 <camel-4.18.3Fix Suggestion:
Update to version camel-4.18.3https://github.com/apache/camel.git (GITHUB):
Affected version(s) >=camel-4.19.0 <camel-4.21.0Fix Suggestion:
Update to version camel-4.21.0https://github.com/apache/camel.git (GITHUB):
Affected version(s) >=camel-4.0.0 <camel-4.14.8Fix Suggestion:
Update to version camel-4.14.8org.apache.camel:camel-cometd (JAVA):
Affected version(s) >=4.19.0 <4.21.0Fix Suggestion:
Update to version 4.21.0org.apache.camel:camel-cometd (JAVA):
Affected version(s) >=4.0.0 <4.14.8Fix Suggestion:
Update to version 4.14.8org.apache.camel:camel-cometd (JAVA):
Affected version(s) >=4.15.0 <4.18.3Fix Suggestion:
Update to version 4.18.3Related Resources (5)
Do you need more information?
Contact UsCVSS v4
Base Score:
9.3
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
HIGH
Vulnerable System Availability
HIGH
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
9.8
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
HIGH
Weakness Type (CWE)
Improper Input Validation
EPSS
Base Score:
0.71