# CVE-2026-71300: Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection > Attackers can inject WebSocket headers to redirect or suppress message delivery in Apache Camel routes, requiring an upgrade to fix. - **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 24 Aug 2026 - **Updated:** 25 Aug 2026 - **Also known as:** GHSA-m5r8-w65q-8wjf ## What is CVE-2026-71300? CVE-2026-71300 is a critical vulnerability in Apache Camel, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2026-71300? 6 open source packages ship an affected version, including org.apache.camel:camel-atmosphere-websocket. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-atmosphere-websocket` | Maven | From 4.0.0 | 4.14.9 | | `org.apache.camel:camel-atmosphere-websocket` | Maven | From 4.0.0 | 4.14.9 | | `org.apache.camel:camel-atmosphere-websocket` | Maven | From 4.15.0 | 4.18.4 | | `org.apache.camel:camel-atmosphere-websocket` | Maven | From 4.15.0 | 4.18.4 | | `org.apache.camel:camel-atmosphere-websocket` | Maven | From 4.19.0 | 4.22.0 | | `org.apache.camel:camel-atmosphere-websocket` | Maven | From 4.19.0 | 4.22.0 | Products: Apache Camel. ## How do I fix CVE-2026-71300? Upgrade org.apache.camel:camel-atmosphere-websocket to a fixed version for your release line: 4.14.9, 4.18.4 or 4.22.0. ## Is CVE-2026-71300 being exploited? There is no known exploitation of CVE-2026-71300 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-71300 (Apache Camel camel-atmosphere-websocket dispatch header injection) — Camel Spring Boot (github_poc): https://github.com/oscerd/CVE-2026-71300 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-78329](https://insights.sbomify.com/CVE-2026-78329/): Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-71300 and fix it if it is affected. What it is: CVE-2026-71300 is a critical vulnerability in Apache Camel, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-71300 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-atmosphere-websocket (Maven): affected from 4.0.0; fixed in 4.14.9 - org.apache.camel:camel-atmosphere-websocket (Maven): affected from 4.0.0; fixed in 4.14.9 - org.apache.camel:camel-atmosphere-websocket (Maven): affected from 4.15.0; fixed in 4.18.4 - org.apache.camel:camel-atmosphere-websocket (Maven): affected from 4.15.0; fixed in 4.18.4 - org.apache.camel:camel-atmosphere-websocket (Maven): affected from 4.19.0; fixed in 4.22.0 - org.apache.camel:camel-atmosphere-websocket (Maven): affected from 4.19.0; fixed in 4.22.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-71300/ (Markdown: https://insights.sbomify.com/CVE-2026-71300/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-71300 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-71300 - OSV: https://osv.dev/vulnerability/CVE-2026-71300 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-71300/ Summaries are generated and may contain mistakes; the official description above is the record.