Unvalidated CometD Headers Enable Message Header Injection

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

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

Apache Camel's cometd component contains a critical input validation flaw that allows attackers to inject arbitrary message headers into Camel exchanges. The vulnerability stems from the CamelCometdBinding class copying the entire ext.CamelHeaders map from untrusted CometD client messages directly onto Camel message objects without filtering or validation. This enables attackers to manipulate internal Camel control headers such as CamelHttpUri, CamelFileName, and CamelJmsDestinationName—headers that should only be set by trusted framework components. Any application using the camel-cometd component to process messages from untrusted CometD clients is vulnerable to header injection attacks that could lead to message routing hijacking, file system manipulation, or message broker exploitation.

Casky's extended reasoning capabilities across 322 mapped security skills detect this vulnerability by correlating two critical MITRE ATT&CK techniques: TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky will observe detection patterns showing how attackers probe for vulnerable cometd endpoints (reconnaissance activity) before injecting malicious headers to route messages to unintended destinations or trigger unsafe operations (initial access and lateral movement). The platform identifies the root cause—CWE-20 Improper Input Validation—by analyzing message header flows and flag when untrusted external data bypasses HeaderFilterStrategy controls. Security teams will see findings highlighting the absence of header validation in message binding logic, with specific recommendations to implement HeaderFilterStrategy filters and apply allowlist-based header validation before processing any CometD client-supplied headers.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

322 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-46454.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-46454

Casky has 322 skills that investigate the attack patterns behind CVE-2026-46454. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn