CVE-2026-55993 Apache Camel-Atmosphere-Websocket: The inbound consumer maps externally-supplied WebSocket query parameters into the Exchange without a HeaderFilterStrategy

High 7.5 Published Updated

Attackers can inject Camel headers via WebSocket query parameters to trigger SSRF and disclose sensitive environment variables or secrets.

Exploited in the wild
Not known
Login needed
Not needed
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-55993?

CVE-2026-55993 is a high-severity server-side request forgery vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

Official description

Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Atmosphere Websocket Component.

The camel-atmosphere-websocket consumer mapped inbound WebSocket query parameters into the Camel Exchange header map without applying any HeaderFilterStrategy (WebsocketConsumer.sendEventNotification() iterates the query-string map collected in WebsocketConsumer.service() and copies each entry into the Exchange). Because nothing blocked the Camel header namespace, a client connecting to the WebSocket endpoint could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTP_URI) - simply by supplying them as query parameters. In a route where the WebSocket consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values and sent to the attacker, disclosing environment variables, application properties and vault secrets. When the WebSocket endpoint is exposed without authentication, this is reachable by an unauthenticated remote attacker. 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 makes the consumer apply the HeaderFilterStrategy it already inherits from the HTTP/servlet stack, filtering the Camel header namespace case-insensitively on inbound mapping, so externally-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from the inbound message before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), require authentication on the WebSocket endpoint, and avoid bridging an untrusted consumer directly into an HTTP producer whose target URI can be driven from message headers.

Weakness: CWE-918, CWE-200, CWE-20

Which versions are affected by CVE-2026-55993?

6 open source packages ship an affected version, including org.apache.camel:camel-atmosphere-websocket. It affects 1 product.

PackageAffectedFixed in
org.apache.camel:camel-atmosphere-websocket MavenFrom 4.0.04.14.8
org.apache.camel:camel-atmosphere-websocket MavenFrom 4.0.04.14.8
org.apache.camel:camel-atmosphere-websocket MavenFrom 4.15.04.18.3
org.apache.camel:camel-atmosphere-websocket MavenFrom 4.15.04.18.3
org.apache.camel:camel-atmosphere-websocket MavenFrom 4.19.04.21.0
org.apache.camel:camel-atmosphere-websocket MavenFrom 4.19.04.21.0

Products include Apache Camel.

How do I fix CVE-2026-55993?

Upgrade org.apache.camel:camel-atmosphere-websocket to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0.

Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.

Is CVE-2026-55993 being exploited?

There is no known exploitation of CVE-2026-55993 in the wild and no public exploit code.

Public exploit code: 1 proofs of concept on GitHub.

All Apache Camel vulnerabilities

Sources

Also known as GHSA-rcvm-6r79-cf4r.

Is CVE-2026-55993 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free