Vulnerabilities in pkg:maven/org.apache.camel/camel-iggy
PACKAGECVE-2026-55994 is a HIGH (CVSS 7.5) the inbound consumer maps externally-supplied vulnerability (CWE-20: Improper Input Validation) affecting Apache Camel-Iggy libraries in the Maven ecosystem. The issue involves the inbound consumer maps externally-supplied iggy message user-headers into the exchange without a headerfilterstrategy. Remediation is available by upgrading affected packages to version 4.18.3, 4.21.0.
pkg:maven/org.apache.camel/camel-iggy
Vulnerability advisories affecting package pkg:maven/org.apache.camel/camel-iggy. Select an advisory below to view technical details or fixes.
| Advisory ID | CVE / NVD | Severity | Summary |
|---|---|---|---|
| GHSA-pw9q-pq7c-rfqw | CVE-2026-55994 | HIGH | Apache Camel-Iggy: The inbound consumer maps externally-supplied Iggy message user-headers into the Exchange without a HeaderFilterStrategy |
CVE-2026-55994 at a Glance
Security Impact
CVSS: 7.5
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
How to Fix CVE-2026-55994
To remediate this vulnerability, upgrade all affected Apache Camel-Iggy dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-iggy</artifactId>
<version>4.18.3</version>
</dependency>
<dependency>
<groupId>org.apache.camel</groupId>
<artifactId>camel-iggy</artifactId>
<version>4.21.0</version>
</dependency>
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
mvn dependency:tree -Dincludes=org.apache.camel
How to Check if You Are Affected
To determine whether your Java application is affected by CVE-2026-55994, inspect your build dependencies using the Maven Dependency Plugin:
mvn dependency:tree -Dincludes=org.apache.camel
Analyze the terminal output to locate any version of Apache Camel-Iggy in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.18.3), your application is affected.
Note: The mvn dependency:tree -Dincludes=org.apache.camel command inspects the resolved dependency graph declared in your project's POM files; it does not perform automated security scanning or inspect runtime dynamic classpaths. Always verify runtime container classpaths and shaded JARs.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-20: Improper Input Validation, where the product receives input or data, but it does not validate or incorrectly validates that the input has the properties that are required to process the data safely and correctly. In Apache Camel-Iggy, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-55994 Affected Apache Camel-Iggy Versions
2 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
org.apache.camel:camel-iggy
|
Maven |
≥ 4.17.0
< 4.18.3
|
4.18.3
|
|
org.apache.camel:camel-iggy
|
Maven |
≥ 4.19.0
< 4.21.0
|
4.21.0
|
References
Frequently Asked Questions
What is CVE-2026-55994?
Which Apache Camel-Iggy versions are affected?
What version fixes CVE-2026-55994?
Is camel-iggy affected?
What is the CVSS score of CVE-2026-55994?
What CWE is associated with CVE-2026-55994?
How can I check Maven dependencies for CVE-2026-55994?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-pw9q-pq7c-rfqw",
"modified" : "2026-08-28T20:09:38Z",
"published" : "2026-07-06T09:30:30Z",
"aliases" : [ "CVE-2026-55994" ],
"summary" : "Apache Camel-Iggy: The inbound consumer maps externally-supplied Iggy message user-headers into the Exchange without a HeaderFilterStrategy",
"details" : "Improper Input Validation, Exposure of Sensitive Information to an Unauthorized Actor, Server-Side Request Forgery (SSRF) vulnerability in Apache Camel in Iggy component.\n\nThe 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.\nThis issue affects Apache Camel: from 4.17.0 before 4.18.3, from 4.19.0 before 4.21.0.\n\nUsers 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.",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.camel:camel-iggy"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.17.0"
}, {
"fixed" : "4.18.3"
} ]
} ]
}, {
"package" : {
"ecosystem" : "Maven",
"name" : "org.apache.camel:camel-iggy"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "4.19.0"
}, {
"fixed" : "4.21.0"
} ]
} ]
} ],
"references" : [ {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-55994"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/23285"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/pull/23313"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/commit/1e776238202edb9d98972cff558e12b53e499647"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/commit/88c43e3af36013585b5483c671950f30e5833a5f"
}, {
"type" : "WEB",
"url" : "https://camel.apache.org/security/CVE-2026-55994.html"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/apache/camel"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/releases/tag/camel-4.18.3"
}, {
"type" : "WEB",
"url" : "https://github.com/apache/camel/releases/tag/camel-4.21.0"
}, {
"type" : "WEB",
"url" : "https://issues.apache.org/jira/browse/CAMEL-23532"
}, {
"type" : "WEB",
"url" : "http://www.openwall.com/lists/oss-security/2026/07/05/28"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-20", "CWE-918" ],
"severity" : "HIGH",
"github_reviewed" : true,
"github_reviewed_at" : "2026-08-28T20:09:38Z",
"nvd_published_at" : "2026-07-06T09:16:39Z"
}
}