CVE-2026-46454: Apache Camel improper input validation in Cometd component

CVE-2026-46454 · Severity: critical · CVSS 9.8 · Published 2026-07-06

Apache Camel is an open-source integration framework used to build message-driven workflows that route data between different systems. The CometD component, which allows real-time bidirectional communication, accepts inbound message headers without filtering, permitting unauthenticated attackers to inject control headers that influence downstream behavior. An attacker could exploit this to redirect HTTP traffic, modify file operations, or alter message destinations, depending on which producers are active in the route.

Technologies: Apache Camel. Vendors: Apache, Maven.

Quick answers

Is CVE-2026-46454 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-46454 being exploited in the wild.
How severe is CVE-2026-46454?
Critical severity, with a CVSS score of 9.8, published 6 July 2026.
Which products and versions are affected?
Apache Camel 4.0.0 to 4.14.7, 4.15.0 to 4.18.2, 4.19.0 to 4.20.x; Apache Camel-CometD 4.0.0 to 4.14.7, 4.15.0 to 4.18.2, 4.19.0 to 4.20.x; org.apache.camel:camel-cometd (Maven) ECOSYSTEM:introduced=4.0.0,fixed=4.14.8.
Is there a fix for CVE-2026-46454?
Yes. org.apache.camel:camel-cometd (Maven): upgrade to 4.14.8 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-46454 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-46454?
Check whether you run Apache Camel, Apache Camel-CometD or org.apache.camel:camel-cometd (Maven) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • org.apache.camel:camel-cometd (Maven): upgrade to 4.14.8 or later
    # set org.apache.camel:camel-cometd to 4.14.8 in your pom.xml or build.gradle

Technical details

The vulnerability is an improper input validation flaw in the camel-cometd component. The CometdBinding.populateExchangeFromMessage method copies the entire ext.CamelHeaders map from inbound Bayeux messages directly onto the Camel Exchange message without applying a HeaderFilterStrategy. Because the CometdComponent installs no Bayeux SecurityPolicy by default, any client completing the Bayeux handshake can publish such messages without authentication. An attacker can inject Camel-reserved header names (CamelHttpUri, CamelFileName, CamelJmsDestinationName, etc.) that persist across internal hops (direct, seda, vm), influencing downstream producers to perform unintended actions such as SSRF, file manipulation, or message redirection. The fix, available in Camel 4.21.0, 4.18.3, and 4.14.8, implements a HeaderFilterStrategy that strips inbound Camel* and camel* headers case-insensitively.

Affected products

  • Apache Camel 4.0.0 to 4.14.7, 4.15.0 to 4.18.2, 4.19.0 to 4.20.x
  • Apache Camel-Cometd 4.0.0 to 4.14.7, 4.15.0 to 4.18.2, 4.19.0 to 4.20.x

Identifiers

  • CVE-2026-46454
  • GHSA-r9cc-j7wr-p329

Timeline

  • 2026-07-06: disclosed: Publicly disclosed via GitHub Advisory
  • 2026-07-06: patched: Patches released: 4.21.0, 4.18.3, 4.14.8

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.