Apache Camel’s Atmosphere WebSocket consumer incorrectly forwards every query‑string parameter it receives into the Camel Exchange header map without filtering. Because the consumer does not apply a HeaderFilterStrategy, an attacker can inject Camel‑internal control headers—including CamelHttpUri (Exchange.HTTP_URI)—through the WebSocket query string. When the message later reaches an HTTP producer, the injected header redirects the server‑side HTTP request to an attacker‑chosen destination, enabling Server‑Side Request Forgery. The HTTP producer also resolves property placeholders in the URI, so the attacker can obtain environment variables, application properties, or vault secrets embedded in the injected value. The flaw is exploitable over an unauthenticated WebSocket connection, allowing any remote actor to trigger internal HTTP calls or disclose privileged information.

The vulnerability exists in the Apache Camel Atmosphere WebSocket component distributed by the Apache Software Foundation. Affected releases are Apache Camel 4.0.0 through 4.14.7, 4.15.0 through 4.18.2, and 4.19.0 through 4.20.x. Users on the 4.14.x LTS stream should upgrade to 4.14.8, those on the 4.18.x stream to 4.18.3, and all other users to 4.21.0, the version that introduces a HeaderFilterStrategy to block inbound Camel‑header injection.

The CVSS score of 7.5 reflects high severity, but the EPSS score of <1% indicates that the exploitation likelihood is currently very low. This vulnerability is not listed in the CISA KEV catalog. The attack vector is a fully remote and unauthenticated WebSocket connection, making the flaw accessible to any remote actor. An attacker with the ability to craft a WebSocket URL can inject control headers and potentially cause server‑side HTTP requests to arbitrary endpoints, expose sensitive configuration data, or access internal services, which can lead to significant confidentiality, integrity, or availability impact.