Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-71300: CWE-20 Improper input validation in Apache Software Foundation Apache Camel

0
High
VulnerabilityCVE-2026-71300cvecve-2026-71300cwe-20
Published: 08/24/2026 (08/24/2026, 16:21:17 UTC)
Source: CVE Database V5
Vendor/Project: Apache Software Foundation
Product: Apache Camel

Description

An improper input validation vulnerability exists in the Apache Camel Atmosphere Websocket component. This flaw allows an external sender to manipulate WebSocket message dispatch headers, potentially causing messages intended for one client to be suppressed or delivered to a different client. The issue affects multiple Apache Camel versions from 4.0.0 up to but not including fixed versions. Users are advised to upgrade to fixed versions or apply header-stripping mitigations to prevent exploitation.

Affected software

Apache Software Foundation/org.apache.camel:camel-atmosphere-websocket
pkg:maven/Apache Software Foundation/org.apache.camel:camel-atmosphere-websocket
Affected versions
>=4.0.0 <4.14.9>=4.15.0 <4.18.4>=4.19.0 <4.22.0

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/24/2026, 17:07:51 UTC

Technical Analysis

CVE-2026-71300 is an improper input validation vulnerability in the Apache Camel Atmosphere Websocket component. The vulnerability arises because certain WebSocket dispatch headers (websocket.connectionKey, websocket.connectionKey.list, websocket.sendToAll, websocket.eventType, websocket.errorType) fall outside the Camel namespace filtering and can be manipulated by an external HTTP sender. This allows an attacker to override the producer's dispatch decision, potentially redirecting or suppressing messages intended for specific WebSocket clients. The issue affects Apache Camel versions from 4.0.0 before 4.14.9, from 4.15.0 before 4.18.4, and from 4.19.0 before 4.22.0. The vulnerability dates back to the introduction of these headers in version 2.17.0 and was fixed by renaming the headers into the Camel namespace, which is a breaking change for routes that set them by literal string. The recommended fix is upgrading to Apache Camel 4.22.0, 4.14.9, or 4.18.4 depending on the release stream. For those unable to upgrade immediately, stripping the dispatch headers at the trust boundary before the producer is advised.

Potential Impact

An attacker who can send HTTP requests to a route bridging an HTTP consumer to an Atmosphere WebSocket producer can manipulate WebSocket dispatch headers. This can cause messages intended for one connected client to be suppressed or delivered to a different client whose connection key is known to the attacker. This undermines message delivery integrity and confidentiality within the WebSocket communication managed by Apache Camel. There is no indication of remote code execution or system compromise, but message routing can be hijacked.

Mitigation Recommendations

A fix is available in Apache Camel versions 4.22.0, 4.14.9, and 4.18.4. Users should upgrade to these versions to remediate the vulnerability. For deployments unable to upgrade immediately, it is recommended to strip the dispatch headers (e.g., using removeHeaders("websocket.*")) at the trust boundary before the Atmosphere WebSocket producer. Additionally, avoid bridging an untrusted HTTP consumer directly into a WebSocket producer whose dispatch is header-driven without stripping these headers first. Note that the fix renames header string values into the Camel namespace, which may require route adjustments if headers are set by literal strings.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
apache
Date Reserved
2026-08-05T17:09:08.388Z
Cvss Version
null
State
PUBLISHED
Remediation Level
null

Threat ID: 6a8c76e0acd9273b49d9f01b

Added to database: 08/24/2026, 16:52:48 UTC

Last enriched: 08/24/2026, 17:07:51 UTC

Last updated: 08/24/2026, 17:15:58 UTC

Views: 5

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses