High, CVSS 7.5MavenPublished
Apache Camel-Iggy: The inbound consumer maps externally-supplied Iggy message user-headers into the Exchange without a HeaderFilterStrategy
CVE-2026-55994 · GHSA-pw9q-pq7c-rfqw
- Affected
- Maven org.apache.camel:camel-iggy >= 4.17.0, < 4.18.3; >= 4.19.0, < 4.21.0
- Fixed in
- 4.21.04.18.3· Vendor fix available
- Issue
- Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Iggy component. The camel-iggy consumer mapped the user-headers of inbound Iggy messages into the Camel Exchange header map without applying any HeaderFilterStrategy (IggyFetchRecords copied the message user-headers straight into the Exchange). Because nothing blocked the Camel header namespace, an actor able to publish to the consumed Iggy stream/topic could set Camel-internal control headers - including CamelHttpUri (Exchange.HTTPURI) - simply by supplying them as message user-headers. In a route where the Iggy consumer feeds a downstream HTTP producer, the injected CamelHttpUri redirects the server-side HTTP request to an attacker-chosen destination (server-side request forgery - for example to an internal service or a cloud metadata endpoint). In addition, the HTTP producer resolves Camel property placeholders on the resulting…
Recommended action: Upgrade to 4.21.0 or 4.18.3 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.