CVE-2026-71300
Received Received - Intake

Improper Input Validation in Apache Camel Atmosphere Websocket

Vulnerability report for CVE-2026-71300, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-08-24

Last updated on: 2026-08-24

Assigner: Apache Software Foundation

Description

Improper input validation vulnerability in Apache Camel Atmosphere Websocket component. This issue affects Apache Camel: from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, from 4.19.0 before 4.22.0. The camel-atmosphere-websocket producer selects which connected WebSocket peers a message is delivered to through Exchange headers, and the string values of those headers sat outside the Camel namespace: websocket.connectionKey and websocket.connectionKey.list, along with websocket.sendToAll, websocket.eventType and websocket.errorType. WebsocketEndpoint extends ServletEndpoint and so inherits HttpHeaderFilterStrategy, which filters only the Camel and camel prefixes; the dotted names therefore fell outside the filtered namespace and were admitted in both directions by every HTTP-family consumer. In a route bridging an HTTP consumer into an atmosphere-websocket producer, an external sender could supply the list header and take over the producer's dispatch decision. WebsocketProducer.process tests the list header before the single-key header, so an injected value discarded the recipient the route had selected: a notification intended for one connected client could be suppressed, or delivered instead to a different client whose connection key the sender knows. The header need not be a query parameter and need not be supplied as a list literally - Camel's HTTP binding promotes a repeated header name, and a bracketed value, to a List when mapping onto the Exchange - so an ordinary inbound HTTP header is sufficient to reach the list-valued branch. This is distinct from CVE-2026-55993, which concerns the consumer-side query-parameter path in the same component. The behaviour dates back to the introduction of these constants, first released in 2.17.0, and was unchanged until this fix. Users are recommended to upgrade to version 4.22.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.9. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.4. For deployments that cannot upgrade immediately, strip the dispatch headers at the trust boundary before the producer, for example with removeHeaders(β€œwebsocket.*”) placed between the HTTP consumer and the atmosphere-websocket producer. Note that the fix renames the header string values into the Camel namespace, which is a breaking change for routes that set them by literal string: routes referencing the WebsocketConstants fields symbolically are unaffected, and the change is documented in the upgrade guides. As defence in depth, do not bridge an untrusted HTTP consumer directly into a WebSocket producer whose dispatch is header-driven without stripping the dispatch namespace first.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-08-24
Last Modified
2026-08-24
Generated
2026-08-24
AI Q&A
2026-08-24
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 12 associated CPEs
Vendor Product Version / Range
apache camel 4.0.0
apache camel 4.14.9
apache camel 4.15.0
apache camel 4.18.4
apache camel 4.19.0
apache camel 4.22.0
apache camel 2.17.0
apache camel 4.14.8
apache camel 4.18.3
apache camel From 4.14.9 (inc)
apache camel From 4.18.4 (inc)
apache camel From 4.22.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-20 The product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This is an improper input validation vulnerability in Apache Camel's Atmosphere Websocket component. An external attacker can manipulate WebSocket dispatch headers through HTTP requests to control message routing to connected clients. The headers used for routing decisions were not properly filtered, allowing unauthorized injection of values like websocket.connectionKey and websocket.connectionKey.list. This could cause messages intended for one client to be delivered to another or suppressed entirely.

Detection Guidance

To detect this vulnerability, inspect HTTP headers in requests targeting Apache Camel Atmosphere WebSocket endpoints. Look for headers like websocket.connectionKey, websocket.connectionKey.list, websocket.sendToAll, websocket.eventType, or websocket.errorType. Use tools like tcpdump, Wireshark, or application logs to capture and analyze HTTP traffic for these specific headers.

Impact Analysis

If you use affected Apache Camel versions with the Atmosphere Websocket component, an attacker could intercept or redirect messages between your system and connected WebSocket clients. This might lead to data leakage, unauthorized access to sensitive information, or disruption of WebSocket-based services. The impact depends on how the component is used in your infrastructure.

Compliance Impact

This vulnerability could potentially violate data protection requirements under GDPR and HIPAA by enabling unauthorized access to or interception of sensitive data transmitted via WebSocket connections. Organizations using affected versions may face compliance risks if message integrity and confidentiality cannot be guaranteed.

Mitigation Strategies

Upgrade Apache Camel to version 4.22.0 or apply the appropriate patch for your release stream (4.14.9 for 4.14.x LTS or 4.18.4 for 4.18.x). As a temporary workaround, strip websocket.* headers between the HTTP consumer and WebSocket producer using removeHeaders("websocket.*") in your route configuration.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-71300. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart