Apache Camel up to 3.22.3/4.8.4/4.10.1 Header internal special elements

Summaryinfo

A vulnerability, which was classified as problematic, was found in Apache Camel up to 3.22.3/4.8.4/4.10.1. This affects an unknown function of the component Header Handler. Executing a manipulation can lead to improper neutralization of internal special elements. This vulnerability is registered as CVE-2025-29891. It is possible to launch the attack remotely. No exploit is available. You should upgrade the affected component.

Detailsinfo

A vulnerability has been found in Apache Camel up to 3.22.3/4.8.4/4.10.1 and classified as problematic. This vulnerability affects some unknown functionality of the component Header Handler. The manipulation with an unknown input leads to a improper neutralization of internal special elements vulnerability. The CWE definition for the vulnerability is CWE-164. The product receives input from an upstream component, but it does not neutralize or incorrectly neutralizes internal special elements that could be interpreted in unexpected ways when they are sent to a downstream component. As an impact it is known to affect integrity. CVE summarizes:

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

The weakness was published by Ryan Barnett. The advisory is shared for download at camel.apache.org. This vulnerability was named CVE-2025-29891 since 03/12/2025. The exploitation appears to be easy. The attack can be initiated remotely. No form of authentication is required for a successful exploitation. There are neither technical details nor an exploit publicly available. The current price for an exploit might be approx. USD $0-$5k (estimation calculated on 03/13/2025).

Upgrading to version 3.22.4, 4.8.5 or 4.10.2 eliminates this vulnerability.

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Productinfo

Vendor

• Apache

Name

• Camel

Version

• 3.22.0
• 3.22.1
• 3.22.2
• 3.22.3
• 4.8.0
• 4.8.1
• 4.8.2
• 4.8.3
• 4.8.4
• 4.10.0
• 4.10.1

License

• open-source

Website

• Vendor: https://www.apache.org/

CPE 2.3info

• 🔍
• 🔍
• 🔍

CPE 2.2info

• 🔍
• 🔍
• 🔍

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

VulDB is the best source for vulnerability data and more expert information about this specific topic.

Discussion