CVE-2025-29891mediumobserved exploitationCWE-164

CVE-2025-29891: medium-severity vulnerability in Apache Camel

Apache Camel: Camel Message Header Injection through request parameters

Published · Updated

77Vexday Risk Score

Prioritize patching. It exploitation observed by VulnCheck and has a public proof of concept.

ssvc Actcvss 4.8epss 76%
from disclosure to weapon225 days
Published on NVDMar 12
1st PoC+225d
VulnCheck+113d
exploitation probability
76%top 1% of all CVEs
observed exploitation
yesVulnCheck
1 public exploit(s)
What the vendors declare (VEX)

Official vendor statements in CSAF/VEX format: whether their product is affected, already fixed, or ruled out — and why. These are the vendor's assertions, not Vexday's judgment.

Affected
4 products (13 components)
Red Hat Fuse 7 · Red Hat Integration Camel K 1 · Red Hat Process Automation 7 · Red Hat Single Sign-On 7
workaround: As a workaround, users could use removeHeaders EIP, to filter out anything like ‘cAmel, cAMEL’ etc, or in general everything not starting with ‘Camel’, ‘camel’ or ‘org.apache.camel.’.
Not affected
2 products (6 components) — because the vulnerable code is not present in the product
Red Hat build of Apache Camel for Spring Boot 4 · Red Hat build of Apache Camel 4 for Quarkus 3
Bypass/Injection vulnerability in Apache Camel. This issue affects Apache Camel: from 4.10.0 before 4.10.2, from 4.8.0 before 4.8.5, from 3.10.0 before 3.22.4. Users are recommended to upgrade to version 4.10.2 for 4.10.x LTS, 4.8.5 for 4.8.x LTS and 3.22.4 for 3.x releases. This vulnerability is present in Camel's default incoming header filter, that allows an attacker to include Camel specific headers that for some Camel components can alter the behaviours such as the camel-bean component, or the camel-exec component. If you have Camel applications that are directly connected to the internet via HTTP, then an attacker could include parameters in the HTTP requests that are sent to the Camel application that get translated into headers.  The headers could be both provided as request parameters for an HTTP methods invocation or as part of the payload of the HTTP methods invocation. All the known Camel HTTP component such as camel-servlet, camel-jetty, camel-undertow, camel-platform-http, and camel-netty-http would be vulnerable out of the box. This CVE is related to the CVE-2025-27636: while they have the same root cause and are fixed with the same fix, CVE-2025-27636 was assumed to only be exploitable if an attacker could add malicious HTTP headers, while we have now determined that it is also exploitable via HTTP parameters. Like in CVE-2025-27636, exploitation is only possible if the Camel route uses particular vulnerable components.
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:L
⚠ Public resources, to assess the exposure of systems you control or are authorized to test. Test only with authorization.