Skip to content
VulniPulse
High7.5Apache Software Foundation

CVE-2026-55994: Apache Camel: Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery

This Apache advisory covers CVE-2026-55994 in Apache Camel.

Open the Apache advisory

Key facts

Vendor rating
High, CVSS 7.5
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N · base score 7.5, scored by CISA-ADPAttack vector: network. Attack complexity: low. Privileges required: none. User interaction: none. Scope: unchanged. Confidentiality impact: high. Integrity impact: none. Availability impact: none.
Weakness
  • CWE-20 Improper Input Validation
  • CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
  • CWE-918 Server-Side Request Forgery (SSRF)
EPSS
0.63% chance of exploitation in the next 30 days (50th percentile). FIRST EPSS, .
CISA SSVC
Exploitation: none observed. Automatable: yes. Technical impact: partial. CISA, .
CISA KEV
Not listed (catalogue checked )
Affected
4.17.0 through 4.18.3; 4.19.0 through 4.21.0.
Fixed in
4.21.0, 4.18.3
Source published
Source revised
Listed by VulniPulse
Record changed

Compiled by VulniPulse from the linked sources. How records are collected and checked.

Affected products & platforms

Apache Software FoundationMessaging

Description

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.

Text from the source record.

Affected versions
  • 4.17.0 through 4.18.3
  • 4.19.0 through 4.21.0.

Official advisory · high-confidence parse· fetched ·verify at source

How to fix CVE-2026-55994

Upgrade to the first fixed release for your version, shown in the table above.

Vendor guidance

  • Users are recommended to upgrade to version 4.21.0, which fixes the issue.

Workarounds

  • 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.

Apache Software Foundation advisories, July 2026All Apache Software Foundation advisories

Get an email when Apache Messaging (ActiveMQ/Kafka/Pulsar) publishes the next one.

See Apache Messaging (ActiveMQ/Kafka/Pulsar)'s last 90 days first. Live alerts for one product are free for life; every vendor is US$15 a month after a free month.

Alert me about Apache Messaging (ActiveMQ/Kafka/Pulsar)