{"answers":{"affected":"6 open source packages ship an affected version, including org.apache.camel:camel-support. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27636 exists.","fix":"Upgrade org.apache.camel:camel-support to a fixed version for your release line: 3.22.4, 4.8.5 or 4.10.2.","what":"CVE-2025-27636 is a medium-severity code injection vulnerability in Apache Camel, published on 9 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2025-27636 and fix it if it is affected.\n\nWhat it is: CVE-2025-27636 is a medium-severity code injection vulnerability in Apache Camel, published on 9 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-27636 exists.\n\nAffected packages and fixed versions:\n- org.apache.camel:camel-support (Maven): affected from 3.10.0; fixed in 3.22.4\n- org.apache.camel:camel-support (Maven): affected from 3.10.0; fixed in 3.22.4\n- org.apache.camel:camel-support (Maven): affected from 4.0.0-M1; fixed in 4.8.5\n- org.apache.camel:camel-support (Maven): affected from 4.0.0-M1; fixed in 4.8.5\n- org.apache.camel:camel-support (Maven): affected from 4.9.0; fixed in 4.10.2\n- org.apache.camel:camel-support (Maven): affected from 4.9.0; fixed in 4.10.2\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-27636/ (Markdown: https://insights.sbomify.com/CVE-2025-27636/index.md)","id":"CVE-2025-27636","markdown":"https://insights.sbomify.com/CVE-2025-27636/index.md","name":"CVE-2025-27636","record":{"aliases":["GHSA-2c2h-2855-mf97"],"analysis":{"component_type":"library","fix_type":"upgrade","impacts":["code_execution","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Apache Camel integration framework","requires_auth":"none","summary":"Attackers can inject malicious headers to alter application behavior, potentially executing unintended code or redirecting messages in Apache Camel applications.","user_interaction":"not_required","vuln_class":"code_injection"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"apache","cpe":[{"product":"camel","vendor":"apache"}],"cvss":{"score":5.6,"severity":"medium","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-178","name":"Improper Handling of Case Sensitivity"}],"description":"Bypass/Injection vulnerability in Apache Camel components under particular conditions.\n\nThis issue affects Apache Camel: from 4.10.0 through \u003c= 4.10.1, from 4.8.0 through \u003c= 4.8.4, from 3.10.0 through \u003c= 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\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\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\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  *  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\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\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.\".","ecosystems":["Maven"],"exploits":{"exploitdb":0,"first_seen":"2025-03-09","github_poc":5,"max_poc_stars":41,"metasploit":0,"nuclei":0,"refs":[{"date":"2025-03-09T09:42:11Z","kind":"github_poc","ref":"https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC","stars":41,"title":null},{"date":"2025-05-14T05:34:03Z","kind":"github_poc","ref":"https://github.com/enochgitgamefied/CVE-2025-27636-Practical-Lab","stars":0,"title":null},{"date":"2025-10-23T09:54:50Z","kind":"github_poc","ref":"https://github.com/Crystallen1/CVE-2025-27636-demo","stars":0,"title":null},{"date":"2026-07-08T18:10:21Z","kind":"github_poc","ref":"https://github.com/oscerd/CVE-2026-40453","stars":0,"title":"Reproducer for CVE-2026-40453: Apache Camel case-variant Camel header injection (incomplete fix of CVE-2025-27636)"},{"date":"2026-09-10T00:00:24Z","kind":"github_poc","ref":"https://github.com/AC8999/CVE-2025-27636-RCE-in-Apache-Camel","stars":0,"title":"CVE-2025-27636 PoC written in Python"}],"tier":"weaponised"},"has_fix":true,"headline":"Apache Camel: Camel Message Header Injection via Improper Filtering","id":"CVE-2025-27636","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"Maven","product":"apache:camel","products":["apache:camel"],"type":"code_injection","year":"2025"},"n_packages":6,"n_references":3,"next":{"headline":"Cross-site scripting in n/a","id":"CVE-2025-27637"},"packages":[{"ecosystem":"Maven","fixed":["3.22.4"],"introduced":["3.10.0"],"last_affected":[],"package":"org.apache.camel:camel-support","purl":null,"source":"GHSA-2c2h-2855-mf97"},{"ecosystem":"Maven","fixed":["3.22.4"],"introduced":["3.10.0"],"last_affected":[],"package":"org.apache.camel:camel-support","purl":"pkg:maven/org.apache.camel/camel-support","source":"GHSA-2c2h-2855-mf97"},{"ecosystem":"Maven","fixed":["4.8.5"],"introduced":["4.0.0-M1"],"last_affected":[],"package":"org.apache.camel:camel-support","purl":null,"source":"GHSA-2c2h-2855-mf97"},{"ecosystem":"Maven","fixed":["4.8.5"],"introduced":["4.0.0-M1"],"last_affected":[],"package":"org.apache.camel:camel-support","purl":"pkg:maven/org.apache.camel/camel-support","source":"GHSA-2c2h-2855-mf97"},{"ecosystem":"Maven","fixed":["4.10.2"],"introduced":["4.9.0"],"last_affected":[],"package":"org.apache.camel:camel-support","purl":null,"source":"GHSA-2c2h-2855-mf97"},{"ecosystem":"Maven","fixed":["4.10.2"],"introduced":["4.9.0"],"last_affected":[],"package":"org.apache.camel:camel-support","purl":"pkg:maven/org.apache.camel/camel-support","source":"GHSA-2c2h-2855-mf97"}],"prev":{"headline":"Cross-site scripting in TRMTracker","id":"CVE-2025-27633"},"products":["Apache Camel"],"published":"2025-03-09","related":[{"cvss_score":10,"headline":"Apache camel-coap allows header injection that can lead to remote code execution","id":"CVE-2026-33453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.9,"headline":"Apache Camel has an incomplete fix for CVE-2025-27636","id":"CVE-2026-40453","kev_date_added":null,"published":"2026-04-27"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod","id":"CVE-2026-80351","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects","id":"CVE-2026-80352","kev_date_added":null,"published":"2026-09-10"},{"cvss_score":9.8,"headline":"Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection","id":"CVE-2026-71300","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes","id":"CVE-2026-78329","kev_date_added":null,"published":"2026-08-24"},{"cvss_score":9.8,"headline":"Apache Camel-PQC: The AWS Secrets Manager key-lifecycle manager deserializes persisted key metadata with java.io.ObjectInputStream and no ObjectInputFilter","id":"CVE-2026-43867","kev_date_added":null,"published":"2026-07-06"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-02-26","vendors":["Apache Software Foundation"]},"summary":"Attackers can inject malicious headers to alter application behavior, potentially executing unintended code or redirecting messages in Apache Camel applications.","url":"https://insights.sbomify.com/CVE-2025-27636/"}