Read the docs
TI-2026-34157 Aliases CVE-2026-46454GHSA-r9cc-j7wr-p329

Improper input validation in Apache Camel

Priority MEDIUM 50CWE-20Published · Updated

Key facts

Attack vector
Network
Privileges required
None
User interaction
None
Attack complexity
Low
Impact type
—
Confidentiality · integrity · availability
High · High · High
Fix status
Fixed

Attack profile from CVSS 3.1 · CISA ADP. Fix status from CNA and GitHub.

Summary

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.

Why it matters now

Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.00827 57th percentileScored 2026-11-07
Fix Fixed Apache Camel (Apache Software Foundation): 4.14.8, 4.18.3, 4.21.0org.apache.camel:camel-cometd (Maven): 4.14.8, 4.18.3, 4.21.0

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation
None
Automatable
Yes
Technical impact
Total

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

VendorProductAffected versionsFixed inStatusSource
ApacheApache Camel4.0.0 to before 4.14.8; 4.15.0 to before 4.18.3; 4.19.0 to before 4.21.04.14.8, 4.18.3, 4.21.0Patch availableCNA
—org.apache.camel:camel-cometd (Maven)4.0.0 to before 4.14.84.14.8Patch availableGHSA-r9cc-j7wr-p329
—org.apache.camel:camel-cometd (Maven)4.15.0 to before 4.18.34.18.3Patch availableGHSA-r9cc-j7wr-p329
—org.apache.camel:camel-cometd (Maven)4.19.0 to before 4.21.04.21.0Patch availableGHSA-r9cc-j7wr-p329
  • Apache Camel VendorApache Affected 4.0.0 to before 4.14.8; 4.15.0 to before 4.18.3; 4.19.0 to before 4.21.0 Fixed in 4.14.8, 4.18.3, 4.21.0 Patch available CNA
  • org.apache.camel:camel-cometd (Maven) Vendor— Affected 4.0.0 to before 4.14.8 Fixed in 4.14.8 Patch available GHSA-r9cc-j7wr-p329
  • org.apache.camel:camel-cometd (Maven) Vendor— Affected 4.15.0 to before 4.18.3 Fixed in 4.18.3 Patch available GHSA-r9cc-j7wr-p329
  • org.apache.camel:camel-cometd (Maven) Vendor— Affected 4.19.0 to before 4.21.0 Fixed in 4.21.0 Patch available GHSA-r9cc-j7wr-p329

CPE configurations NVD · 1

CPEVersionsRoleVendor
cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*4.0.0 to before 4.14.8; 4.15.0 to before 4.18.3; 4.19.0 to before 4.21.0VulnerableApache
  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:* Versions 4.0.0 to before 4.14.8; 4.15.0 to before 4.18.3; 4.19.0 to before 4.21.0 Vulnerable ·Apache

Remediation

  • Fix · CNA Apache Camel (Apache Software Foundation) Fixed in 4.14.8, 4.18.3, 4.21.0
  • Fix · GHSA-r9cc-j7wr-p329 org.apache.camel:camel-cometd (Maven) Fixed in 4.14.8 Advisory →
  • Fix · GHSA-r9cc-j7wr-p329 org.apache.camel:camel-cometd (Maven) Fixed in 4.18.3 Advisory →
  • Fix · GHSA-r9cc-j7wr-p329 org.apache.camel:camel-cometd (Maven) Fixed in 4.21.0 Advisory →

Fixed in the same release

Records fixed by the same vendor advisory or release, as the CNA lists them.

  • Release ·

    Apache Camel 4.14.8, 4.18.3, 4.21.0

    14 records Highest priority Priority MEDIUM 7 MEDIUM, 7 LOW

    Other records, highest priority first

    • TI-2026-35614 Improper input validation in Apache CamelPriority MEDIUM 50
    • TI-2026-34159 Improper input validation in Apache CamelPriority MEDIUM 50
    • TI-2026-35613 Improper input validation in Apache CamelPriority MEDIUM 48

Timeline

  1. 2026-10-02 Threatist record created from CVE-2026-46454
  2. 2026-10-03 Alias added: GHSA-r9cc-j7wr-p329

References

  • TI-2026-76322 Unsafe deserialization in Apache Camel camel-hazelcast CVSS 4.0CRITICAL 10.0
  • TI-2026-18973 Apache Camel: Camel-Keycloak: Cross-Realm Token Acceptance Bypass in KeycloakSecurityPolicy CVSS 3.1CRITICAL 9.1
  • TI-2026-76339 Path traversal in Apache Camel azure-files component CVSS 3.1CRITICAL 9.1
  • TI-2026-76330 Path traversal in Apache Camel FTP consumer escapes polled directory CVSS 3.1CRITICAL 9.1
  • TI-2025-20435 Apache Camel: Camel Message Header Injection via Improper Filtering CVSS 3.1MEDIUM 5.6
  • TI-2026-34899 Apache Camel: Camel-CXF Message Header Injection via Missing Inbound Filtering CVSS 3.1CRITICAL 9.8
See all 116 →

Sources