Summary
CVE-2026-71300 is an improper input validation vulnerability (CWE-20) in the camel-atmosphere-websocket component of Apache Camel. It allows a remote, unauthenticated attacker to inject WebSocket dispatch headers via crafted HTTP requests, hijacking the producer’s message-routing decision so that notifications intended for one connected client are redirected to another client or suppressed entirely. CISA’s ADP assessment rates this CRITICAL with a CVSS v3.1 base score of 9.8.
Technical details
- Root cause: The
camel-atmosphere-websocketproducer selects which connected WebSocket client(s) receive a message based on Exchange headers such aswebsocket.connectionKey.list,websocket.connectionKey, andwebsocket.sendToAll. These header names use dots rather than theCamel/camelprefix, so Camel’s HTTP header filter (HttpHeaderFilterStrategy), which only strips headers in the Camel namespace, does not remove them. - Trigger conditions: The vulnerability applies to Camel routes that bridge an HTTP consumer to a
camel-atmosphere-websocketproducer, where inbound HTTP requests can carry arbitrary attacker-controlled headers through to the producer. - Attack vector: Network — an attacker sends an HTTP request (e.g., a POST to a notification endpoint) containing an injected
websocket.connectionKey.list(or similar) header value, causing the producer to dispatch the message to a connection key of the attacker’s choosing instead of the intended recipient. - Impact: Full compromise of the producer’s dispatch logic — an attacker can intercept messages meant for a legitimate peer, redirect notifications to a connection they control, or silently suppress delivery to the intended client.
Affected software
- Apache Camel
camel-atmosphere-websocket, versions 4.0.0 through 4.14.8 - Apache Camel
camel-atmosphere-websocket, versions 4.15.0 through 4.18.3 - Apache Camel
camel-atmosphere-websocket, versions 4.19.0 through 4.21.x
Severity
CVSS v3.1 Base Score: 9.8 (Critical)
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Mitigation and recommended actions
- Immediate: Upgrade to the fixed release for your branch — 4.14.9 (LTS), 4.18.4, or 4.22.0. These releases rename the dispatch header constants to Camel-namespaced form (e.g.,
CamelAtmosphereWebsocketConnectionKey), so routes referencing the old literal string headers must be updated accordingly. - If immediate patching is not possible: Insert
removeHeaders("websocket.*")in the route between the HTTP consumer and the WebSocket producer to strip attacker-supplied dispatch headers before they reach the producer. Also consider requiring authentication on endpoints that feed the WebSocket producer and avoid bridging untrusted HTTP input directly into WebSocket dispatch logic.
How IONIX identifies potentially affected assets
IONIX matches the following signals against data already collected when it crawled the asset; identifying the technology sends no request beyond that crawl.
- Response header
x-powered-by:Apache Camelfollowed by a version number (e.g.,Apache Camel 4.14.8)

