{"id":"CVE-2025-27636","published":"2025-03-09T12:09:58Z","modified":"2026-02-26T19:09:44Z","title":"Apache Camel: Camel Message Header Injection via Improper Filtering","vendor":"Apache Software Foundation","product":"Apache Camel","tier":"core","eol":null,"affectedVersions":[{"vendor":"Apache Software Foundation","product":"Apache Camel","versions":[">= 4.10.0, < 4.10.2",">= 4.8.0, < 4.8.5",">= 3.10.0, < 3.22.4"]}],"description":{"text":"Bypass/Injection vulnerability in Apache Camel components under particular conditions.\n\nThis 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.\n\nUsers 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.\n\n\n\nThis vulnerability is present in Camel's default incoming header filter, that allows an attacker to include Camel specific\n\nheaders that for some Camel components can alter the behaviours such as the camel-bean component, to call another method\n\non the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send\n\nthe 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\n\n\n\n\nThe attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are\n\ndirectly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests\n\nthat are send to the Camel application.\n\n\n\n\nAll 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.\n\nIn 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.\n\nIn terms of usage of the default header filter strategy the list of components using that is: \n\n\n  *  camel-activemq\n  *  camel-activemq6\n  *  camel-amqp\n  *  camel-aws2-sqs\n  *  camel-azure-servicebus\n  *  camel-cxf-rest\n  *  camel-cxf-soap\n  *  camel-http\n  *  camel-jetty\n  *  camel-jms\n  *  camel-kafka\n  *  camel-knative\n  *  camel-mail\n  *  camel-nats\n  *  camel-netty-http\n  *  camel-platform-http\n  *  camel-rest\n  *  camel-sjms\n  *  camel-spring-rabbitmq\n  *  camel-stomp\n  *  camel-tahu\n  *  camel-undertow\n  *  camel-xmpp\n\n\n\n\n\n\nThe vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \"Camel\", \"camel\", or \"org.apache.camel.\". \n\n\nMitigation: 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.\".","provenance":"source","from":"CVE.org"},"summary":null,"cvss":{"score":5.6,"severity":"MEDIUM","version":"3.1","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","provenance":"source","from":"CISA ADP Vulnrichment"},"epss":{"score":0.97057,"percentile":0.99891,"date":"2026-10-29","provenance":"source"},"kev":null,"vulncheckKev":{"dateAdded":"2025-04-07","exploitedFirstSeen":"2025-04-07","ransomware":false,"evidence":[{"url":"https://www.akamai.com/blog/security/early-and-accurate-response-to-apache-camel-cves","date":"2025-04-07"},{"url":"https://unit42.paloaltonetworks.com/apache-cve-2025-24813-cve-2025-27636-cve-2025-29891/","date":"2025-07-03"},{"url":"https://www.loginsoft.com/reports/annually/vulnerability-intelligence-report-2025","date":"2026-01-20"}],"evidenceTotal":3,"provenance":"source"},"exploited":true,"otx":{"pulseCount":6,"pulses":[{"name":"ACTUALIZACION | Oracle Critical Patch Update Advisory - April 2026","url":"https://otx.alienvault.com/pulse/6a04aeed763730d81a39cece","created":"2026-05-13"},{"name":"Apache Under the Lens: Tomcat's Partial PUT and Camel's Header Hijack","url":"https://otx.alienvault.com/pulse/6891b05bc3719860351030eb","created":"2025-08-05"},{"name":"Actualización Oracle update - 20/07/2025","url":"https://otx.alienvault.com/pulse/687d031c402a7679a4673a5d","created":"2025-07-20"},{"name":"IOC - Apache Under the Lens: Tomcat's Partial PUT and Camel's Header Hijack","url":"https://otx.alienvault.com/pulse/68672f190b11f7c470dc7005","created":"2025-07-04"},{"name":"Apache Under the Lens: Tomcat's Partial PUT and Camel's Header Hijack","url":"https://otx.alienvault.com/pulse/6866650f9a525176d0fa51dc","created":"2025-07-03"},{"name":"Apache Under the Lens: Tomcat’s Partial PUT and Camel’s Header Hijack","url":"https://otx.alienvault.com/pulse/68665f5478d358eb41baf18c","created":"2025-07-03"}],"provenance":"machine"},"cwes":[{"id":"CWE-178","name":"Improper Handling of Case Sensitivity"}],"references":[{"url":"https://lists.apache.org/thread/l3zcg3vts88bmc7w8172wkgw610y693z","tags":["vendor-advisory"]},{"url":"https://issues.apache.org/jira/browse/CAMEL-21828","tags":["issue-tracking"]},{"url":"https://camel.apache.org/security/CVE-2025-27636.html","tags":["vendor-advisory"]},{"url":"http://www.openwall.com/lists/oss-security/2025/03/09/1","tags":[]},{"url":"https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC/blob/main/src/main/java/com/example/camel/VulnerableCamel.java","tags":["exploit"]},{"url":"https://camel.apache.org/security/CVE-2025-27636.txt.asc","tags":["vendor-advisory"]}],"techniques":[],"reports":[],"affected":[{"ecosystem":"Maven","package":"org.apache.camel:camel-support","vulnerableRanges":[">=3.10.0, <3.22.4",">=4.0.0-M1, <4.8.5",">=4.9.0, <4.10.2"],"patched":["3.22.4","4.8.5","4.10.2"],"from":["GHSA-2c2h-2855-mf97"],"provenance":"source"}],"advisories":[{"id":"GHSA-2c2h-2855-mf97","url":"https://github.com/advisories/GHSA-2c2h-2855-mf97","severity":"MODERATE","ecosystem":"Maven","package":"org.apache.camel:camel-support","vulnerableRanges":[">=3.10.0, <3.22.4"],"patched":["3.22.4"],"provenance":"source","from":"GHSA"},{"id":"GHSA-2c2h-2855-mf97","url":"https://github.com/advisories/GHSA-2c2h-2855-mf97","severity":"MODERATE","ecosystem":"Maven","package":"org.apache.camel:camel-support","vulnerableRanges":[">=4.0.0-M1, <4.8.5"],"patched":["4.8.5"],"provenance":"source","from":"GHSA"},{"id":"GHSA-2c2h-2855-mf97","url":"https://github.com/advisories/GHSA-2c2h-2855-mf97","severity":"MODERATE","ecosystem":"Maven","package":"org.apache.camel:camel-support","vulnerableRanges":[">=4.9.0, <4.10.2"],"patched":["4.10.2"],"provenance":"source","from":"GHSA"}],"euvd":{"id":"EUVD-2025-6662","url":"https://euvd.enisa.europa.eu/vulnerability/EUVD-2025-6662","exploited":false,"exploitedSince":null,"provenance":"source"},"exploits":[],"exploitSources":{"pocGithub":{"count":3,"skipped":2,"earliest":"2025-03-09","earliestUrl":"https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC","repos":[{"name":"akamai/CVE-2025-27636-Apache-Camel-PoC","url":"https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC","stars":41,"created":"2025-03-09"},{"name":"oscerd/CVE-2026-40453","url":"https://github.com/oscerd/CVE-2026-40453","stars":0,"created":"2026-07-08"},{"name":"AC8999/CVE-2025-27636-RCE-in-Apache-Camel","url":"https://github.com/AC8999/CVE-2025-27636-RCE-in-Apache-Camel","stars":0,"created":"2026-09-10"}]},"first":{"date":"2025-03-09","source":"PoC-in-GitHub","url":"https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC"},"provenance":"source"},"exploitRefs":["https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC/blob/main/src/main/java/com/example/camel/VulnerableCamel.java"],"flow":[],"timeline":[{"date":"2025-03-09","kind":"published","label":"Published (CVE.org)","url":"https://www.cve.org/CVERecord?id=CVE-2025-27636","provenance":"source"},{"date":"2025-03-09","kind":"exploit-public","label":"First public exploit: PoC-in-GitHub","url":"https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC","provenance":"source"},{"date":"2025-04-07","kind":"exploited-reported","label":"Exploitation first reported (VulnCheck KEV evidence)","url":"https://www.akamai.com/blog/security/early-and-accurate-response-to-apache-camel-cves","provenance":"source"}],"speed":{"daysToPublicExploit":0,"firstExploitFrom":"PoC-in-GitHub","daysToKev":null},"priority":{"score":65.8,"factors":[{"name":"In a KEV catalog","points":35.0,"detail":"listed in VulnCheck KEV"},{"name":"Recent KEV listing","points":0.0,"detail":"added 571 days ago"},{"name":"Known ransomware use","points":0.0,"detail":"not known"},{"name":"EPSS percentile","points":19.98,"detail":"percentile 0.9989"},{"name":"Named in threat reports","points":0.0,"detail":"0 reports"},{"name":"Public exploit code","points":5.0,"detail":"1 NVD reference tagged Exploit; 3 PoC-in-GitHub repos"},{"name":"Mentioned in OTX pulses","points":1.92,"detail":"6 pulses"},{"name":"CVSS severity","points":3.92,"detail":"base score 5.6"},{"name":"End-of-life product","points":0.0,"detail":"supported or unknown"}]},"lineage":{"familyId":"fam-apache-camel-cve-2025-27636","children":[{"from":"CVE-2025-27636","to":"CVE-2026-40453","relation":"variant","confidence":"high","kind":"lineage","evidence":[{"kind":"text","provenance":"source","relation":"variant","quote":"The fix for CVE-2025-27636 added setLowerCase(true) to HttpHeaderFilterStrategy so that case-variant header names such as 'CAmelExecCommandExecutable' are filtered out alongside 'CamelExecCommandExecutable'.","from":"CVE.org","in":"CVE-2026-40453"}]},{"from":"CVE-2025-27636","to":"CVE-2025-29891","relation":"related","confidence":"low","kind":"lineage","evidence":[{"kind":"text","provenance":"source","relation":"related","quote":"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 determine…","from":"CVE.org","in":"CVE-2025-29891"}]}]}}