MAVEN · JULY 2026 · EARLY WARNING

Apache Camel Cometd Component Vulnerability: Critical CVE Alert

EARLY WARNING · UNCONFIRMED. This page describes a developing threat that 0Day surfaced from early signals and has not yet independently confirmed. Details may change. Always verify against the primary sources before acting.

Severity: HIGH
Affected component: apache-camel-cometd (maven)
Patched version: 4.21.0

GHSA-R9CC-J7WR-P329

An early warning has been issued for a critical vulnerability in the Apache Camel Cometd Component. This vulnerability allows unauthenticated clients to inject Camel control headers.

What happened

An improper input validation vulnerability has been identified in the Apache Camel Cometd Component. This vulnerability, tracked as GHSA-R9CC-J7WR-P329, allows unauthenticated clients to inject Camel control headers due to the absence of a HeaderFilterStrategy in the mapping of inbound Bayeux message headers into the Exchange. This issue affects Apache Camel versions from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, and from 4.19.0 before 4.21.0.

The vulnerability was first flagged on July 6, 2026. It is currently under investigation and has not been exploited in the wild. Users of affected versions are advised to upgrade to mitigate potential risks.

What to do about it

Upgrade to Apache Camel version 4.21.0 to mitigate the vulnerability.
For 4.14.x LTS releases, upgrade to 4.14.8.
For 4.18.x releases, upgrade to 4.18.3.
Monitor the primary sources for updates on the vulnerability and any further developments.

How 0Day would have caught this

MATCHED TO YOUR ACTUAL DEPENDENCY GRAPH0Day matches every incoming threat signal against your GitHub organization’s full dependency graph, including transitive dependencies. If apache-camel-cometd is anywhere in your dependency tree, the engineers who own the affected repositories get a push alert the moment it is flagged — no manual audit to remember to run.

Read how this differs from waiting on a scanner to catch a known advisory, or see the exact, read-only access 0Day needs to do this for an organization.

Frequently asked questions

Am I affected?

You are affected if you are using Apache Camel versions from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, or from 4.19.0 before 4.21.0.

What should I do right now?

Upgrade to Apache Camel version 4.21.0. For 4.14.x LTS releases, upgrade to 4.14.8. For 4.18.x releases, upgrade to 4.18.3.

Is this vulnerability being exploited in the wild?

No, this vulnerability has not been exploited in the wild according to the current information.

Sources

[GHSA-r9cc-j7wr-p329] Apache Camel-Cometd: Inbound Bayeux message headers are mapped into the Exchange without a HeaderFilterStrategy, allowing unauthenticated clients to inject Camel control headers

Join the 0Day waitlist →

← Back to all threats