Server-side Request Forgery (SSRF) Affecting org.apache.camel:camel-vertx-websocket package, versions [,4.14.8)[4.15.0,4.18.3)[4.19.0,4.21.0)
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applications- Snyk IDSNYK-JAVA-ORGAPACHECAMEL-17881055
- published7 Jul 2026
- disclosed6 Jul 2026
- creditKamalpreet Singh
Introduced: 6 Jul 2026
NewCVE-2026-46726 (opens in a new tab)How to fix?
Upgrade org.apache.camel:camel-vertx-websocket to version 4.14.8, 4.18.3, 4.21.0 or higher.
Overview
Affected versions of this package are vulnerable to Server-side Request Forgery (SSRF) via the VertxWebsocketConsumer inbound header mapping in components/camel-vertx/camel-vertx-websocket. An attacker can redirect server-side HTTP requests and disclose sensitive values by sending WebSocket query or path parameters named like Camel control headers, such as CamelHttpUri, to an exposed WebSocket endpoint. The consumer copied those externally supplied parameters into the Camel Exchange header map without filtering the Camel header namespace, so a downstream HTTP producer could be driven to an attacker-chosen URI and resolve attacker-controlled placeholders. In routes that bridge the WebSocket consumer into HTTP, this exposes internal services, metadata endpoints, environment variables, application properties, and vault secrets to an unauthenticated remote client.