WaratekVRT Sign in

CVE-2026-46454 Apache Camel

Affected softwareApache Camel
Severity9.8 Critical CVSS 3.1
Fixed in4.14.8, 4.18.3, 4.21.0
WeaknessImproper input validation (CWE-20)
Published6 Jul 2026
Updated25 Oct 2026

Description

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.

Exploitation status

No public exploit

No exploit has been reported in the sources we check. The 1 repository below are public GitHub repositories with fewer than 5 stars.

  • CISA KEV not listed
  • VulnCheck KEV not listed
  • CISA Vulnrichment exploitation: none
  • Indexed PoC 1 indexed, none at 5+ stars
  • EPSS 0.83% chance in 30 days

1 of these are GitHub repositories with fewer than 5 stars. They are listed for reference and don't count toward the exploitation status above.

IndexArtifactStarsFirst seen
GitHub PoC Reproducer for CVE-2026-46454 — Apache Camel camel-cometd inbound Bayeux header injection (unauthenticated Camel control-header injection → downstream producer steering / RCE) 2026-07-13

Waratek protection

No exploit published

Within Waratek scope. In the sources we check, nobody has published exploit code for this CVE or reported it being exploited.

A public code fix exists: apache/camel #23211.

  • Protection none
  • Action unverified
  • Review automated Upstream data
  • Record active
Decided by Exploit code for this candidate, published in a reviewed catalogue or a GitHub repository with 5 or more stars, or in use per CISA or VulnCheck; not only a CISA verdict, a forecast, or nothing at all
Finding This CVE is not listed in CISA KEV or VulnCheck KEV, CISA Vulnrichment records no active exploitation, no reviewed exploit catalogue carries an entry for it, and no GitHub PoC repository for it has 5 or more stars. Nobody has published exploit code worth tracing, so it is not a candidate for a rule ahead of the ones where somebody has; an upstream fix path does exist, so the remediation half of the candidacy still holds. This is a statement about what has been published, not about whether the defect is reachable or serious.

Affected software and releases

Maven packages

Affected and fixed versions, from OSV.dev
PackageIntroducedFixedLast affected
org.apache.camel:camel-cometd 4.0.0 4.14.8 unbounded
org.apache.camel:camel-cometd 4.15.0 4.18.3 unbounded
org.apache.camel:camel-cometd 4.19.0 4.21.0 unbounded

Products and versions

2 products, 6 version entries
SourceVendorProductSchemeAffected versions
nvd apache camel generic ≥ 4.0.0 and < 4.14.8 · ≥ 4.15.0 and < 4.18.3 · ≥ 4.19.0 and < 4.21.0
osv org.apache.camel camel-cometd generic ≥ 4.0.0 and < 4.14.8 · ≥ 4.15.0 and < 4.18.3 · ≥ 4.19.0 and < 4.21.0

References

URLTags
https://github.com/apache/camel/pull/23211 WEB
https://github.com/apache/camel/commit/6fad391f9f5257b93ce07d9b8e5e7f486210d4f5 WEB
https://github.com/apache/camel/commit/e20bdc2a6a3fd1128bcebe1b64c8e8589f0bc57d WEB
https://github.com/apache/camel/commit/e9c741b4908dcffc0e1a7b1a5e6207a46aaac608 WEB
https://camel.apache.org/security/CVE-2026-46454.html WEB
https://github.com/apache/camel PACKAGE
https://github.com/apache/camel/releases/tag/camel-4.14.8 WEB
https://github.com/apache/camel/releases/tag/camel-4.18.3 WEB
https://github.com/apache/camel/releases/tag/camel-4.21.0 WEB
https://issues.apache.org/jira/browse/CAMEL-23507 WEB

Timeline

Published2026-07-06By the CVE Program.
NVD record modified2026-10-25NVD's own last-modified date for this record.