Barak Srour

#14534of 56,331
19.6Total CVSS
Vulnerabilities · 2
Critical
2
PT-2026-80928
9.8
2026-08-24
Apache · Apache Camel · CVE-2026-71300
**Name of the Vulnerable Software and Affected Versions** Apache Camel versions 4.0.0 through 4.14.8 Apache Camel versions 4.15.0 through 4.18.3 Apache Camel versions 4.19.0 through 4.21.9 **Description** Improper input validation in the Apache Camel Atmosphere Websocket component allows for header injection. The `camel-atmosphere-websocket` producer determines message delivery to WebSocket peers using specific exchange headers: `websocket.connectionKey`, `websocket.connectionKey.list`, `websocket.sendToAll`, `websocket.eventType`, and `websocket.errorType`. Because these headers fall outside the filtered Camel namespace, they are admitted by HTTP-family consumers. In routes bridging an HTTP consumer to an atmosphere-websocket producer, an external sender can supply these headers to manipulate the producer's dispatch decisions. This can lead to notifications being suppressed or delivered to an unintended client. This occurs because the `WebsocketProducer.process()` function prioritizes the list header over the single-key header. **Recommendations** Upgrade to version 4.14.9 for those on the 4.14.x LTS releases stream. Upgrade to version 4.18.4 for those on the 4.18.x releases stream. Upgrade to version 4.22.0 for all other affected versions. As a temporary mitigation, strip dispatch headers at the trust boundary before the producer by using `removeHeaders(“websocket.*”)` between the HTTP consumer and the atmosphere-websocket producer. Avoid bridging an untrusted HTTP consumer directly into a WebSocket producer whose dispatch is header-driven without first stripping the dispatch namespace.
PT-2026-80930
9.8
2026-08-24
Apache · Apache Camel · CVE-2026-78329
**Name of the Vulnerable Software and Affected Versions** Apache Camel versions 4.11.0 through 4.14.8 Apache Camel versions 4.15.0 through 4.18.3 Apache Camel versions 4.19.0 through 4.21.9 **Description** Improper input validation in the Apache Camel Undertow component occurs because the `UndertowEndpoint` incorrectly defaults its `headerFilterStrategy` field to the base `HttpHeaderFilterStrategy`. This action overwrites the `UndertowHeaderFilterStrategy` installed by the `DefaultUndertowHttpBinding`, causing undertow-specific filtering to be bypassed on endpoint-configured routes. Consequently, the legacy `websocket.` Exchange-header prefix is not filtered at the transport boundary. This allows an undertow HTTP consumer to map inbound wire headers onto the Exchange, which an undertow WebSocket producer may then interpret as dispatch directives to deliver messages to an unintended peer. Additionally, header names rejected by undertow are mapped onto the Exchange instead of being skipped. This issue does not affect Rest DSL consumers as they use `UndertowRestHeaderFilterStrategy`. **Recommendations** Upgrade to version 4.14.9 for those on the 4.14.x LTS releases stream. Upgrade to version 4.18.4 for those on the 4.18.x releases stream. Upgrade to version 4.22.0. As a temporary workaround, explicitly configure the strategy by binding an `UndertowHeaderFilterStrategy` in the registry and referencing it on the endpoint, and use `removeHeaders("websocket.*")` to strip dispatch headers at the trust boundary.