Apache Software Foundation Apache Camel
Apache Camel: Camel-Cometd: Inbound Bayeux message headers are mapped into the Exchange without a HeaderFilterStrategy, allowing unauthenticated clients to inject Camel control headers
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 versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 4.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.
References
- Vendor advisory camel.apache.org/security/CVE-2026-46454.html
Timeline
Days relative to CVE publicationFirst public PoC 7.2 days after publication; not in CISA KEV. First PoC: oscerd/CVE-2026-46454 (created 13 Jul 2026, found by us: backfilled).
PoC repositories
Found on GitHub.1 PoCs
PoCs 1
| Repository | Created | Stars | Assessment |
|---|---|---|---|
| oscerd/CVE-2026-46454 | 13 Jul 2026 +7.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-46454
- Evidence
- oscerd/CVE-2026-46454/README.md:94
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-46454 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-46454; classtype:web-application-attack; sid:9645303; rev:1;)
Sigma
Template generated from PoC characteristics. Review before deploying.
title: Apache Software Foundation Apache Camel exploit attempt (CVE-2026-46454)
id: gg-pocmon-cve-2026-46454-9645303
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-46454. Generated, not reviewed.
references:
- https://poc.griffinguard.io/cve/CVE-2026-46454
logsource:
category: webserver
detection:
selection:
cs-method: GET
cs-uri-stem|contains|all:
- '/exploit/attack'
condition: selection
falsepositives:
- Authorized vulnerability scanning
level: critical
tags:
- attack.initial_access
- attack.t1190
- cve.2026.46454