{
  "threat_severity" : "Moderate",
  "public_date" : "2025-03-10T00:00:00Z",
  "bugzilla" : {
    "description" : "camel-http: org.apache.camel: bypass of header filters via specially crafted response",
    "id" : "2350682",
    "url" : "https://bugzilla.redhat.com/show_bug.cgi?id=2350682"
  },
  "cvss3" : {
    "cvss3_base_score" : "6.3",
    "cvss3_scoring_vector" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L",
    "status" : "verified"
  },
  "cwe" : "CWE-644",
  "details" : [ "Bypass/Injection vulnerability in Apache Camel components under particular conditions.\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.\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.\nThis vulnerability is present in Camel's default incoming header filter, that allows an attacker to include Camel specific\nheaders that for some Camel components can alter the behaviours such as the camel-bean component, to call another method\non the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send\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\nThe attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are\ndirectly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests\nthat are send to the Camel application.\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.\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.\nIn terms of usage of the default header filter strategy the list of components using that is: \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\nThe vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \"Camel\", \"camel\", or \"org.apache.camel.\". \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.\".", "A vulnerability was found in Apache Camel. This flaw allows an attacker to bypass filtering via a specially crafted request containing a certain combination of upper and lower case characters due to an issue in the default header filtering mechanism, which blocks headers starting with \"Camel\" or \"camel.\"" ],
  "statement" : "This vulnerability is rated as having Moderate impact because it can only be triggered under certain configurations and does not enable complete takeover of the system. In order to be vulnerable, a system using the Apache Camel Framework must specifically be using the camel-bean component as a producer and the exchange is coming from a http-based consumer, such as HTTP component or platform-http. If exploitation occurs, an attacker could call other methods on that bean already in the classpath, but not from other arbitrary java beans, System.getenv, nor part of JDK itself.",
  "affected_release" : [ {
    "product_name" : "Red Hat build of Apache Camel 4.8.5 for Spring Boot",
    "release_date" : "2025-04-02T00:00:00Z",
    "advisory" : "RHSA-2025:3543",
    "cpe" : "cpe:/a:redhat:apache_camel_spring_boot:4.8.5",
    "package" : "org.apache.camel/camel-http"
  }, {
    "product_name" : "Red Hat build of Apache Camel 4.8.5 for Spring Boot",
    "release_date" : "2025-04-02T00:00:00Z",
    "advisory" : "RHSA-2025:3543",
    "cpe" : "cpe:/a:redhat:apache_camel_spring_boot:4.8.5",
    "package" : "org.apache.camel/camel-http-base"
  }, {
    "product_name" : "Red Hat Build of Apache Camel 4.8 for Quarkus 3.15",
    "release_date" : "2025-03-20T00:00:00Z",
    "advisory" : "RHSA-2025:3091",
    "cpe" : "cpe:/a:redhat:camel_quarkus:3.15",
    "package" : "org.apache.camel/camel-http"
  }, {
    "product_name" : "Red Hat Build of Apache Camel 4.8 for Quarkus 3.15",
    "release_date" : "2025-03-20T00:00:00Z",
    "advisory" : "RHSA-2025:3091",
    "cpe" : "cpe:/a:redhat:camel_quarkus:3.15",
    "package" : "org.apache.camel/camel-http-base"
  } ],
  "package_state" : [ {
    "product_name" : "Red Hat build of Apache Camel 4 for Quarkus 3",
    "fix_state" : "Not affected",
    "package_name" : "org.apache.camel/camel-http-common",
    "cpe" : "cpe:/a:redhat:camel_quarkus:3"
  }, {
    "product_name" : "Red Hat build of Apache Camel for Spring Boot 4",
    "fix_state" : "Not affected",
    "package_name" : "org.apache.camel/camel-http-common",
    "cpe" : "cpe:/a:redhat:camel_spring_boot:4"
  }, {
    "product_name" : "Red Hat build of Apache Camel for Spring Boot 4",
    "fix_state" : "Affected",
    "package_name" : "org.apache.camel.springboot/camel-http-starter",
    "cpe" : "cpe:/a:redhat:camel_spring_boot:4"
  }, {
    "product_name" : "Red Hat Fuse 7",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http",
    "cpe" : "cpe:/a:redhat:jboss_fuse:7"
  }, {
    "product_name" : "Red Hat Fuse 7",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http4",
    "cpe" : "cpe:/a:redhat:jboss_fuse:7"
  }, {
    "product_name" : "Red Hat Fuse 7",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http4-starter",
    "cpe" : "cpe:/a:redhat:jboss_fuse:7"
  }, {
    "product_name" : "Red Hat Fuse 7",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http-base",
    "cpe" : "cpe:/a:redhat:jboss_fuse:7"
  }, {
    "product_name" : "Red Hat Fuse 7",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http-common",
    "cpe" : "cpe:/a:redhat:jboss_fuse:7"
  }, {
    "product_name" : "Red Hat Fuse 7",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http-common-starter",
    "cpe" : "cpe:/a:redhat:jboss_fuse:7"
  }, {
    "product_name" : "Red Hat Fuse 7",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http-starter",
    "cpe" : "cpe:/a:redhat:jboss_fuse:7"
  }, {
    "product_name" : "Red Hat Integration Camel K 1",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http",
    "cpe" : "cpe:/a:redhat:integration:1"
  }, {
    "product_name" : "Red Hat Integration Camel K 1",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http-base",
    "cpe" : "cpe:/a:redhat:integration:1"
  }, {
    "product_name" : "Red Hat Integration Camel K 1",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel/camel-http-common",
    "cpe" : "cpe:/a:redhat:integration:1"
  }, {
    "product_name" : "Red Hat Integration Camel K 1",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel.kafkaconnector/camel-http-kafka-connector",
    "cpe" : "cpe:/a:redhat:integration:1"
  }, {
    "product_name" : "Red Hat Integration Camel K 1",
    "fix_state" : "Out of support scope",
    "package_name" : "org.apache.camel.kafkaconnector/camel-https-kafka-connector",
    "cpe" : "cpe:/a:redhat:integration:1"
  }, {
    "product_name" : "Red Hat JBoss Enterprise Application Platform 8",
    "fix_state" : "Not affected",
    "package_name" : "org.apache.camel/camel-http-common",
    "cpe" : "cpe:/a:redhat:jboss_enterprise_application_platform:8"
  }, {
    "product_name" : "Red Hat JBoss Enterprise Application Platform Expansion Pack",
    "fix_state" : "Not affected",
    "package_name" : "org.apache.camel/camel-http-common",
    "cpe" : "cpe:/a:redhat:jbosseapxp"
  }, {
    "product_name" : "Red Hat Process Automation 7",
    "fix_state" : "Not affected",
    "package_name" : "org.apache.camel/camel-http-common",
    "cpe" : "cpe:/a:redhat:jboss_enterprise_bpms_platform:7"
  }, {
    "product_name" : "Red Hat Single Sign-On 7",
    "fix_state" : "Not affected",
    "package_name" : "org.apache.camel/camel-http-common",
    "cpe" : "cpe:/a:redhat:red_hat_single_sign_on:7"
  } ],
  "references" : [ "https://www.cve.org/CVERecord?id=CVE-2025-27636\nhttps://nvd.nist.gov/vuln/detail/CVE-2025-27636\nhttps://github.com/apache/camel/commit/781491b446921341f87a13824be4f7b5063776fc\nhttps://lists.apache.org/thread/l3zcg3vts88bmc7w8172wkgw610y693z" ],
  "name" : "CVE-2025-27636",
  "mitigation" : {
    "value" : "Remove headers from your Camel routes; this can be accomplished in several ways, including globally or per route.",
    "lang" : "en:us"
  },
  "csaw" : false
}