Skip to content
Fencer Vulns
medium 5.6

CVE-2025-27636 json

Apache Camel: Camel Message Header Injection via Improper Filtering

published 2025-03-09 20 mo ago modified 2026-06-17 4 mo ago also EUVD-2025-6662 , GHSA-2c2h-2855-mf97

cvss
5.6
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
97.1%
EPSS 97.1% chance of exploitation in 30 days, percentile 99.8%
public exploits
0
none known

Summary

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

Patch / fix

  • maven org.apache.camel:camel-support 3.22.4, 4.8.5, 4.10.2
  • Apache Software Foundation Apache Camel 3.22.4, 4.8.5, 4.10.2

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2025-27636 updated cvss 6.3

camel-http: org.apache.camel: bypass of header filters via specially crafted response

  • Red Hat build of Apache Camel for Spring Boot 4 camel-http-starter
    affected: workaround, no fix available “Remove headers from your Camel routes; this can be accomplished in several ways, including globally or per route.”
  • Red Hat Fuse 7 camel-http, camel-http-base, camel-http-common, org.apache.camel/camel-http4 org.apache.camel/camel-http4, org.apache.camel/camel-http-starter org.apache.camel/camel-http-starter, org.apache.camel/camel-http4-starter org.apache.camel/camel-http4-starter, +1 more Red Hat Integration Camel K 1 camel-http, camel-http-base, camel-http-common, org.apache.camel.kafkaconnector/camel-http-kafka-connector org.apache.camel.kafkaconnector/camel-http-kafka-connector, org.apache.camel.kafkaconnector/camel-https-kafka-connector org.apache.camel.kafkaconnector/camel-https-kafka-connector
    affected: workaround, no fix planned “Remove headers from your Camel routes; this can be accomplished in several ways, including globally or per route.”
  • Red Hat Build of Apache Camel 4.8 for Quarkus 3.15
    fixed: vendor fix “Remove headers from your Camel routes; this can be accomplished in several ways, including globally or per route.” RHSA-2025:3091
  • Red Hat build of Apache Camel 4.8.5 for Spring Boot
    fixed: vendor fix “Remove headers from your Camel routes; this can be accomplished in several ways, including globally or per route.” RHSA-2025:3543
  • Red Hat build of Apache Camel 4 for Quarkus 3 camel-http-common Red Hat build of Apache Camel for Spring Boot 4 camel-http-common Red Hat JBoss Enterprise Application Platform 8 camel-http-common Red Hat JBoss Enterprise Application Platform Expansion Pack camel-http-common Red Hat Process Automation 7 camel-http-common Red Hat Single Sign-On 7 camel-http-common
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
Proof of concept is public
Automatable
no
Technical impact
partial
Assessed
12 mo ago

Exploit prediction

97.06% chance of exploitation in the next 30 days, higher than 99.8% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • github.com https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC/blob/main/src/main/java/com/example/camel/VulnerableCamel.java referenced PoC, tagged "exploit" by a source, unverified
  • camel.apache.org https://camel.apache.org/security/CVE-2025-27636.txt.asc referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
CISA ADP 3.1 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
CNA 3.1 5.6 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel-support
>=3.10.0, <3.22.4
>=4.0.0-M1, <4.8.5
>=4.9.0, <4.10.2
3.22.4
4.8.5
4.10.2

Affected products

  • Apache Software Foundation Apache Camel

Classification

Weakness
  • CWE-178 Improper Handling of Case Sensitivity

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.