Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
6.3
CVE-2025-27636: Apache Camel allows forged headers to change processing
CVE-2025-27636 · published 1 year ago
Summary
Apache Camel versions 3.10.0 through 3.22.3, 4.8.0 through 4.8.4, and 4.10.0 through 4.10.1 may accept malicious message headers that can redirect work to a different method or queue. If your Camel applications are exposed to the internet, an attacker could include specially crafted headers in HTTP requests to alter the intended behavior. Update to the latest releases (3.22.4, 4.8.5, or 4.10.2) to protect against this risk.
What to do
- Update apache org.apache.camel:camel-support to version 3.22.4.
- Update apache org.apache.camel:camel-support to version 4.10.2.
- Update apache org.apache.camel:camel-support to version 4.8.5.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| maven | apache | org.apache.camel:camel-support |
>= 3.10.0, < 3.22.4 >= 4.9.0, < 4.10.2 >= 4.0.0-M1, < 4.8.5 Fix: upgrade to 3.22.4
|
| – | apache | camel |
>= 3.10.0, < 3.22.4 >= 4.8.0, < 4.8.5 >= 4.10.0, < 4.10.2 cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:* |
Original advisory text
Apache Camel: Camel Message Header Injection via Improper Filtering
Bypass/Injection vulnerability in Apache Camel components under particular conditions.
This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from 3.10.0 through <= 3.22.3.
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, to call another method
on the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send
the message to another queue (on the same broker) than was coded in the application. This could also be seen by using the camel-exec component
The attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are
directly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests
that are send to the Camel application.
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.
In these conditions an attacker could be able to forge a Camel header name and make the bean component invoking other methods in the same bean.
In terms of usage of the default header filter strategy the list of components using that is:
* camel-activemq
* camel-activemq6
* camel-amqp
* camel-aws2-sqs
* camel-azure-servicebus
* camel-cxf-rest
* camel-cxf-soap
* camel-http
* camel-jetty
* camel-jms
* camel-kafka
* camel-knative
* camel-mail
* camel-nats
* camel-netty-http
* camel-platform-http
* camel-rest
* camel-sjms
* camel-spring-rabbitmq
* camel-stomp
* camel-tahu
* camel-undertow
* camel-xmpp
The vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with "Camel", "camel", or "org.apache.camel.".
Mitigation: You can easily work around this in your Camel applications by removing the headers in your Camel routes. There are many ways of doing this, also globally or per route. This means you could use the removeHeaders EIP, to filter out anything like "cAmel, cAMEL" etc, or in general everything not starting with "Camel", "camel" or "org.apache.camel.".
This issue affects Apache Camel: from 4.10.0 through <= 4.10.1, from 4.8.0 through <= 4.8.4, from 3.10.0 through <= 3.22.3.
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, to call another method
on the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send
the message to another queue (on the same broker) than was coded in the application. This could also be seen by using the camel-exec component
The attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are
directly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests
that are send to the Camel application.
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.
In these conditions an attacker could be able to forge a Camel header name and make the bean component invoking other methods in the same bean.
In terms of usage of the default header filter strategy the list of components using that is:
* camel-activemq
* camel-activemq6
* camel-amqp
* camel-aws2-sqs
* camel-azure-servicebus
* camel-cxf-rest
* camel-cxf-soap
* camel-http
* camel-jetty
* camel-jms
* camel-kafka
* camel-knative
* camel-mail
* camel-nats
* camel-netty-http
* camel-platform-http
* camel-rest
* camel-sjms
* camel-spring-rabbitmq
* camel-stomp
* camel-tahu
* camel-undertow
* camel-xmpp
The vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with "Camel", "camel", or "org.apache.camel.".
Mitigation: You can easily work around this in your Camel applications by removing the headers in your Camel routes. There are many ways of doing this, also globally or per route. This means you could use the removeHeaders EIP, to filter out anything like "cAmel, cAMEL" etc, or in general everything not starting with "Camel", "camel" or "org.apache.camel.".
References
- https://github.com/apache/camel/commit/23a833eec6131a3cdce6e4b1b40b3ac2035b6adf
- https://github.com/apache/camel/commit/45a6b74f7f8af8fd58f197566938a9534392a624
- https://github.com/apache/camel/blob/camel-4.9.0/core/camel-support/src/main/jav...
- https://camel.apache.org/security/CVE-2025-27636.txt.asc Vendor Advisory
- https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC/blob/main/src/main/jav... Exploit
- https://github.com/advisories/GHSA-2c2h-2855-mf97
- http://www.openwall.com/lists/oss-security/2025/03/09/1 URL
- https://camel.apache.org/security/CVE-2025-27636.html Vendor Advisory
- https://repo.maven.apache.org/maven2 URL
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/27xxx/CVE-2025-27636... Vendor Advisory
- https://lists.apache.org/thread/l3zcg3vts88bmc7w8172wkgw610y693z Vendor Advisory
- https://nvd.nist.gov/vuln/detail/CVE-2025-27636 Vendor Advisory
- https://issues.apache.org/jira/browse/CAMEL-21828 Third Party Advisory
Internet-facing
60 days
Internal
At next upgrade
- Not known to be exploited
- Needs hands-on effort to exploit
- Gives an attacker partial control
Type
CWE-178Improper Handling of Case Sensitivity
Timeline
Published9 Mar 2025
Updated20 Oct 2026
First seen6 Mar 2026
Track software like this
Free during beta