CVE-2026-46454

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.

• CWE-20

• https://camel.apache.org/security/CVE-2026-46454.htmlMitigation, Vendor Advisory
• http://www.openwall.com/lists/oss-security/2026/07/05/7Mailing List, Third Party Advisory

Published

Jul 6, 2026

Last Modified

Jul 8, 2026

Status

Analyzed

• How Strix found a critical auth bypass in etcdStrix autonomously discovered a critical authentication bypass in etcd, later designated CVE-2026-33413.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-46446SOGo before 5.12.7, when PostgreSQL or MariaDB is used, and …7.1
• CVE-2026-46447OpenStack Ironic before 35.0.2 allows Boot Script Injection …7.7
• CVE-2026-46448In OpenStack Nova before 33.0.2, the server create API does …8.5
• CVE-2026-4645Rejected reason: Duplicate of CVE-2026-32287
• CVE-2026-46452Improper Input Validation vulnerability in Apache NimBLE in …5.3
• CVE-2026-46453Improper Input Validation, Authorization Bypass Through User…5.3
• CVE-2026-46455Insufficient Session Expiration vulnerability in Apache Came…9.8
• CVE-2026-46456Improper Input Validation vulnerability in Apache Camel AWS2…9.8
• CVE-2026-46457Improper Input Validation vulnerability in Apache Camel NATS…7.5
• CVE-2026-46458ICU Scandinavia Boomerang is vulnerable to an information di…7.1
• CVE-2026-46459ICU Scandinavia Boomerang is vulnerable to a missing authent…5.3
• CVE-2026-4646Mattermost versions 11.6.x <= 11.6.0, 11.5.x <= 11.5.3, 11.4…4.3