Skip to content

← Actionable
Critical, CVSS 9.8amended

Apache Camel-Atmosphere-Websocket: WebSocket dispatch header injection - the producer selected its target peers through Exchange headers whose names sat outside the filtered Camel namespace

CVE-2026-71300GHSA-m5r8-w65q-8wjf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (org.apache.camel:camel-atmosphere-websocket 4.22.0, 4.18.4, 4.14.9), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2026-71300: 0.74% estimated exploitation activity in the next 30 days; percentile 54.59 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-m5r8-w65q-8wjf

  2. Revision 1 · created ·

    Published from osv record GHSA-m5r8-w65q-8wjf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-71300

Advisory: Apache Camel-Atmosphere-Websocket: WebSocket dispatch header injection - the producer selected its target peers through Exchange headers whose names sat outside the filtered Camel namespace
IDs: CVE-2026-71300, GHSA-m5r8-w65q-8wjf
Record: https://patchnext.com/advisories/cve-2026-71300 (revision 2, source checked 26 Oct 2026, 16:55 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: org.apache.camel:camel-atmosphere-websocket 4.22.0, 4.18.4, 4.14.9. A vendor fix does not mean a deployment is fixed.

## Affected components
- Maven org.apache.camel:camel-atmosphere-websocket: affected >= 4.0.0, < 4.14.9; >= 4.15.0, < 4.18.4; >= 4.19.0, < 4.22.0; fixed in 4.22.0, 4.14.9, 4.18.4

## Suggested inspection (read-only)
- Maven org.apache.camel:camel-atmosphere-websocket: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on org.apache.camel:camel-atmosphere-websocket.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-m5r8-w65q-8wjf (OSV record GHSA-m5r8-w65q-8wjf lists affected ranges: Maven org.apache.camel:camel-atmosphere-websocket >=4.0.0 =4.15.0 =4.19.0 <4.22.0 (fixed))
- Verified: https://github.com/advisories/GHSA-m5r8-w65q-8wjf (GitHub-reviewed advisory GHSA-m5r8-w65q-8wjf lists affected ranges: Maven org.apache.camel:camel-atmosphere-websocket >=4.0.0 =4.15.0 =4.19.0 <4.22.0)

Commands are suggestions: review each one before running it.

Loading voting…