Server-side Request Forgery (SSRF) Affecting org.apache.camel:camel-iggy 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-17821202
- published6 Jul 2026
- disclosed6 Jul 2026
- creditKamalpreet Singh
Introduced: 6 Jul 2026
NewCVE-2026-55993 (opens in a new tab)How to fix?
Upgrade org.apache.camel:camel-iggy 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 WebsocketConsumer.service process. An attacker can redirect server-side HTTP requests to arbitrary destinations and access sensitive environment variables, application properties, or vault secrets by injecting specially crafted WebSocket query parameters that are mapped into internal headers. This is only exploitable if the WebSocket endpoint is exposed without authentication and is bridged directly into an HTTP producer whose target URI can be influenced from message headers.
Workaround
This vulnerability can be mitigated by stripping Camel control headers from inbound messages before they reach any downstream producer (for example, using removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), requiring authentication on the WebSocket endpoint, and avoiding bridging an untrusted consumer directly into an HTTP producer whose target URI can be driven from message headers.