CVE-2026-55994

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.HTTP_URI) - 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 (attacker-controlled) URI, so placeholders embedded in the injected value - such as an environment-variable reference, an application property, or a vault reference - are resolved to their real values and sent to the attacker, disclosing environment variables, application properties and vault secrets. This issue affects Apache Camel: from 4.17.0 before 4.18.3, from 4.19.0 before 4.21.0. Users are recommended to upgrade to version 4.21.0, which fixes the issue. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. The fix adds a dedicated IggyHeaderFilterStrategy (and a headerFilterStrategy endpoint option) that filters the Camel header namespace case-insensitively on inbound mapping, so externally-supplied Camel* / camel* headers are no longer copied into the Exchange. For deployments that cannot upgrade immediately, strip the Camel control headers from the inbound message before they reach any downstream producer (for example removeHeaders('Camel*') and removeHeaders('camel*') at the start of the route), restrict who can publish to the consumed Iggy stream/topic, and avoid bridging an untrusted consumer directly into an HTTP producer whose target URI can be driven from message headers.

• CWE-20
• CWE-200
• CWE-918

• https://camel.apache.org/security/CVE-2026-55994.htmlVendor Advisory
• http://www.openwall.com/lists/oss-security/2026/07/05/28Third Party Advisory

Published

Jul 6, 2026

Last Modified

Jul 9, 2026

Status

Analyzed

• One Click Account Takeover in GranolaHow a notification link broke out of Electron and led to a one-click account takeover.
• Autonomous PentestingAI agents that find and validate exploitable vulnerabilities like this one across your applications.
• PR ReviewsPentest every pull request so vulnerable code is caught before it ships to production.
• AI Penetration TestingHow AI-driven penetration testing continuously covers your attack surface.

• CVE-2026-55980A denial-of-service vulnerability in CatchPulse could allow …5.5
• CVE-2026-55985The web management interface in  Tycon Systems TPDIN-Monitor…5.3
• CVE-2026-5599A user with API access and "manage users" permission in any …7.3
• CVE-2026-55990In NLnet Labs Unbound 1.7.0 up to and including 1.25.1, when…5.9
• CVE-2026-55991In NLnet Labs Unbound 1.22.0 up to and including 1.25.1, a r…5.9
• CVE-2026-55993Improper Input Validation, Exposure of Sensitive Information…7.5
• CVE-2026-55995A Double Free vulnerability in open-iscsi allows an unauthen…8.7
• CVE-2026-55996A denial-of-service vulnerability was identified in multiple…4.3
• CVE-2026-55997Rancher issues long-lived registration tokens to authenticat…8.8
• CVE-2026-55998The endpoint /v3/import/{token}_{clusterId}.yaml retrieves t…5.3
• CVE-2026-55999Local attackers with a X connection able to provide PCX font…7.8
• CVE-2026-5600A new API endpoint introduced in pretix 2025 that is suppose…4.3