Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-71300 – WebSocket Message Hijacking / Dispatch Manipulation – Apache Camel camel-atmosphere

Be the first to know when new zero-days emerge:

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-websocket producer selects which connected WebSocket client(s) receive a message based on Exchange headers such as websocket.connectionKey.list, websocket.connectionKey, and websocket.sendToAll. These header names use dots rather than the Camel/camel prefix, 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-websocket producer, 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 Camel followed by a version number (e.g., Apache Camel 4.14.8)

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge