Apache Camel’s Atmosphere WebSocket consumer incorrectly forwards every query‑string parameter received from a client into the Camel Exchange header map without filtering. Because the Camel header namespace is not blocked, an attacker can inject privileged Camel control headers, notably CamelHttpUri (Exchange.HTTP_URI). When the message is later routed to an HTTP producer, that header causes the server to make a request to an attacker‑chosen URI, enabling server‑side request forgery. Additionally, the HTTP producer expands property placeholders embedded in the injected URI, exposing environment‑variable values, application properties, and vault secrets to the attacker. The flaw is exploitable over an unauthenticated WebSocket connection, making it reachable by any remote actor.

The weakness exists in the Apache Camel Atmosphere WebSocket component distributed by the Apache Software Foundation. Affected releases are 4.0.0 through 4.14.7, 4.15.0 through 4.18.2, and 4.19.0 through 4.20.x. Users of 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 indicates high severity, but the EPSS score of <1% shows that the exploitation likelihood is currently very low. The vulnerability is not found in the CISA KEV catalog. However, because the attack vector is a fully remote and unauthenticated WebSocket connection and can lead to SSRF and disclosure of cryptographically protected information, the potential impact remains significant. An attacker only needs to craft a WebSocket URL with controlled query parameters; without any authentication or additional safeguards, the flaw can be exercised en route, triggering internal HTTP calls or leaking privileged secrets.