{
   containers: {
      adp: [
         {
            providerMetadata: {
               dateUpdated: "2025-03-09T17:02:21.478Z",
               orgId: "af854a3a-2127-422b-91ae-364da2661108",
               shortName: "CVE",
            },
            references: [
               {
                  url: "http://www.openwall.com/lists/oss-security/2025/03/09/1",
               },
            ],
            title: "CVE Program Container",
         },
         {
            metrics: [
               {
                  cvssV3_1: {
                     attackComplexity: "HIGH",
                     attackVector: "NETWORK",
                     availabilityImpact: "LOW",
                     baseScore: 5.6,
                     baseSeverity: "MEDIUM",
                     confidentialityImpact: "LOW",
                     integrityImpact: "LOW",
                     privilegesRequired: "NONE",
                     scope: "UNCHANGED",
                     userInteraction: "NONE",
                     vectorString: "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L",
                     version: "3.1",
                  },
               },
               {
                  other: {
                     content: {
                        id: "CVE-2025-27636",
                        options: [
                           {
                              Exploitation: "poc",
                           },
                           {
                              Automatable: "no",
                           },
                           {
                              "Technical Impact": "partial",
                           },
                        ],
                        role: "CISA Coordinator",
                        timestamp: "2025-03-10T18:51:57.713279Z",
                        version: "2.0.3",
                     },
                     type: "ssvc",
                  },
               },
            ],
            problemTypes: [
               {
                  descriptions: [
                     {
                        cweId: "CWE-178",
                        description: "CWE-178 Improper Handling of Case Sensitivity",
                        lang: "en",
                        type: "CWE",
                     },
                  ],
               },
            ],
            providerMetadata: {
               dateUpdated: "2025-03-10T18:56:43.452Z",
               orgId: "134c704f-9b21-4f2e-91b3-4a467353bcc0",
               shortName: "CISA-ADP",
            },
            references: [
               {
                  tags: [
                     "exploit",
                  ],
                  url: "https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC/blob/main/src/main/java/com/example/camel/VulnerableCamel.java",
               },
               {
                  tags: [
                     "vendor-advisory",
                  ],
                  url: "https://camel.apache.org/security/CVE-2025-27636.txt.asc",
               },
            ],
            title: "CISA ADP Vulnrichment",
         },
      ],
      cna: {
         affected: [
            {
               collectionURL: "https://repo.maven.apache.org/maven2",
               defaultStatus: "unaffected",
               packageName: "org.apache.camel:camel",
               product: "Apache Camel",
               vendor: "Apache Software Foundation",
               versions: [
                  {
                     lessThan: "4.10.2",
                     status: "affected",
                     version: "4.10.0",
                     versionType: "semver",
                  },
                  {
                     lessThan: "4.8.5",
                     status: "affected",
                     version: "4.8.0",
                     versionType: "semver",
                  },
                  {
                     lessThan: "3.22.4",
                     status: "affected",
                     version: "3.10.0",
                     versionType: "semver",
                  },
               ],
            },
         ],
         credits: [
            {
               lang: "en",
               type: "finder",
               value: "Mark Thorson",
            },
         ],
         descriptions: [
            {
               lang: "en",
               supportingMedia: [
                  {
                     base64: false,
                     type: "text/html",
                     value: "<p>Bypass/Injection vulnerability in Apache Camel components under particular conditions.</p><p>This issue affects Apache Camel: from 4.10.0 through &lt;= 4.10.1, from 4.8.0 through &lt;= 4.8.4, from 3.10.0 through &lt;= 3.22.3.</p><p>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.</p><div></div><div>This vulnerability is present in Camel's default incoming header filter, that allows an attacker to include Camel specific</div><div>headers that for some Camel components can alter the behaviours such as the camel-bean component, to call another method</div><div>on the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send</div><div>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</div><div><br></div><div>The attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are</div><div>directly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests</div><div>that are send to the Camel application.</div><div><br></div>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.<br><br>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.<br><br><div>In terms of usage of the default header filter strategy the list of components using that is: <br></div><div><div><ul><li>camel-activemq</li><li>camel-activemq6</li><li>camel-amqp</li><li>camel-aws2-sqs</li><li>camel-azure-servicebus</li><li>camel-cxf-rest</li><li>camel-cxf-soap</li><li>camel-http</li><li>camel-jetty</li><li>camel-jms</li><li>camel-kafka</li><li>camel-knative</li><li>camel-mail</li><li>camel-nats</li><li>camel-netty-http</li><li>camel-platform-http</li><li>camel-rest</li><li>camel-sjms</li><li>camel-spring-rabbitmq</li><li>camel-stomp</li><li>camel-tahu</li><li>camel-undertow</li><li>camel-xmpp</li></ul></div></div><div>The vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \"Camel\", \"camel\", or \"org.apache.camel.\".&nbsp;</div><br><div><span style=\"background-color: var(--wht);\">Mitigation:&nbsp;</span>You can easily work around this in your Camel applications by removing the&nbsp;headers in your Camel routes. There are many ways of doing this, also&nbsp;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.\".&nbsp;<br></div><br>",
                  },
               ],
               value: "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.\".",
            },
         ],
         metrics: [
            {
               other: {
                  content: {
                     text: "moderate",
                  },
                  type: "Textual description of severity",
               },
            },
         ],
         problemTypes: [
            {
               descriptions: [
                  {
                     description: "Bypass/Injection",
                     lang: "en",
                  },
               ],
            },
         ],
         providerMetadata: {
            dateUpdated: "2025-03-17T14:42:57.795Z",
            orgId: "f0158376-9dc2-43b6-827c-5f631a4d8d09",
            shortName: "apache",
         },
         references: [
            {
               tags: [
                  "vendor-advisory",
               ],
               url: "https://lists.apache.org/thread/l3zcg3vts88bmc7w8172wkgw610y693z",
            },
            {
               tags: [
                  "issue-tracking",
               ],
               url: "https://issues.apache.org/jira/browse/CAMEL-21828",
            },
            {
               tags: [
                  "vendor-advisory",
               ],
               url: "https://camel.apache.org/security/CVE-2025-27636.html",
            },
         ],
         source: {
            defect: [
               "CAMEL-21828",
            ],
            discovery: "UNKNOWN",
         },
         title: "Apache Camel: Camel Message Header Injection via Improper Filtering",
         x_generator: {
            engine: "Vulnogram 0.2.0",
         },
      },
   },
   cveMetadata: {
      assignerOrgId: "f0158376-9dc2-43b6-827c-5f631a4d8d09",
      assignerShortName: "apache",
      cveId: "CVE-2025-27636",
      datePublished: "2025-03-09T12:09:58.619Z",
      dateReserved: "2025-03-04T11:56:29.254Z",
      dateUpdated: "2025-03-17T14:42:57.795Z",
      state: "PUBLISHED",
   },
   dataType: "CVE_RECORD",
   dataVersion: "5.1",
   "vulnerability-lookup:meta": {
      nvd: "{\"cve\":{\"id\":\"CVE-2025-27636\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2025-03-09T13:15:34.403\",\"lastModified\":\"2025-03-17T15:15:44.750\",\"vulnStatus\":\"Awaiting Analysis\",\"cveTags\":[],\"descriptions\":[{\"lang\":\"en\",\"value\":\"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.\\\".\"},{\"lang\":\"es\",\"value\":\"Vulnerabilidad de bypass/inyección en el componente Apache Camel-Bean en determinadas condiciones. Este problema afecta a Apache Camel: desde la versión 4.10.0 hasta la &lt;= 4.10.1, desde la versión 4.8.0 hasta la &lt;= 4.8.4, desde la versión 3.10.0 hasta la &lt;= 3.22.3. Se recomienda a los usuarios que actualicen a la versión 4.10.2 para 4.10.x LTS, 4.8.5 para 4.8.x LTS y 3.22.4 para las versiones 3.x. Esta vulnerabilidad solo está presente en la siguiente situación. El usuario está utilizando uno de los siguientes servidores HTTP a través de uno de los siguientes componentes Camel * camel-servlet * camel-jetty * camel-undertow * camel-platform-http * camel-netty-http y en la ruta, el intercambio se enrutará a un productor de camel-bean. Por lo tanto, SOLO el componente camel-bean está afectado. En particular: * La invocación del bean (solo se ve afectada si usas cualquiera de los anteriores junto con el componente camel-bean). * El bean que se puede llamar tiene más de 1 método implementado. En estas condiciones, un atacante podría falsificar un nombre de encabezado de Camel y hacer que el componente bean invoque otros métodos en el mismo bean. La vulnerabilidad surge debido a un error en el mecanismo de filtrado predeterminado que solo bloquea los encabezados que comienzan con \\\"Camel\\\", \\\"camel\\\" u \\\"org.apache.camel\\\". Mitigación: puedes solucionar esto fácilmente en tus aplicaciones Camel eliminando los encabezados en tus rutas Camel. Hay muchas formas de hacer esto, también globalmente o por ruta. Esto significa que puedes usar el EIP removeHeaders para filtrar cualquier cosa como \\\"cAmel, cAMEL\\\", etc., o en general todo lo que no comience con \\\"Camel\\\", \\\"camel\\\" u \\\"org.apache.camel\\\".\"}],\"metrics\":{\"cvssMetricV31\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"cvssData\":{\"version\":\"3.1\",\"vectorString\":\"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L\",\"baseScore\":5.6,\"baseSeverity\":\"MEDIUM\",\"attackVector\":\"NETWORK\",\"attackComplexity\":\"HIGH\",\"privilegesRequired\":\"NONE\",\"userInteraction\":\"NONE\",\"scope\":\"UNCHANGED\",\"confidentialityImpact\":\"LOW\",\"integrityImpact\":\"LOW\",\"availabilityImpact\":\"LOW\"},\"exploitabilityScore\":2.2,\"impactScore\":3.4}]},\"weaknesses\":[{\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"type\":\"Secondary\",\"description\":[{\"lang\":\"en\",\"value\":\"CWE-178\"}]}],\"references\":[{\"url\":\"https://camel.apache.org/security/CVE-2025-27636.html\",\"source\":\"security@apache.org\"},{\"url\":\"https://issues.apache.org/jira/browse/CAMEL-21828\",\"source\":\"security@apache.org\"},{\"url\":\"https://lists.apache.org/thread/l3zcg3vts88bmc7w8172wkgw610y693z\",\"source\":\"security@apache.org\"},{\"url\":\"http://www.openwall.com/lists/oss-security/2025/03/09/1\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\"},{\"url\":\"https://camel.apache.org/security/CVE-2025-27636.txt.asc\",\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\"},{\"url\":\"https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC/blob/main/src/main/java/com/example/camel/VulnerableCamel.java\",\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\"}]}}",
      vulnrichment: {
         containers: "{\"adp\": [{\"title\": \"CVE Program Container\", \"references\": [{\"url\": \"http://www.openwall.com/lists/oss-security/2025/03/09/1\"}], \"providerMetadata\": {\"orgId\": \"af854a3a-2127-422b-91ae-364da2661108\", \"shortName\": \"CVE\", \"dateUpdated\": \"2025-03-09T17:02:21.478Z\"}}, {\"title\": \"CISA ADP Vulnrichment\", \"metrics\": [{\"cvssV3_1\": {\"scope\": \"UNCHANGED\", \"version\": \"3.1\", \"baseScore\": 5.6, \"attackVector\": \"NETWORK\", \"baseSeverity\": \"MEDIUM\", \"vectorString\": \"CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L\", \"integrityImpact\": \"LOW\", \"userInteraction\": \"NONE\", \"attackComplexity\": \"HIGH\", \"availabilityImpact\": \"LOW\", \"privilegesRequired\": \"NONE\", \"confidentialityImpact\": \"LOW\"}}, {\"other\": {\"type\": \"ssvc\", \"content\": {\"id\": \"CVE-2025-27636\", \"role\": \"CISA Coordinator\", \"options\": [{\"Exploitation\": \"poc\"}, {\"Automatable\": \"no\"}, {\"Technical Impact\": \"partial\"}], \"version\": \"2.0.3\", \"timestamp\": \"2025-03-10T18:51:57.713279Z\"}}}], \"references\": [{\"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\"]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"type\": \"CWE\", \"cweId\": \"CWE-178\", \"description\": \"CWE-178 Improper Handling of Case Sensitivity\"}]}], \"providerMetadata\": {\"orgId\": \"134c704f-9b21-4f2e-91b3-4a467353bcc0\", \"shortName\": \"CISA-ADP\", \"dateUpdated\": \"2025-03-10T18:51:42.884Z\"}}], \"cna\": {\"title\": \"Apache Camel: Camel Message Header Injection via Improper Filtering\", \"source\": {\"defect\": [\"CAMEL-21828\"], \"discovery\": \"UNKNOWN\"}, \"credits\": [{\"lang\": \"en\", \"type\": \"finder\", \"value\": \"Mark Thorson\"}], \"metrics\": [{\"other\": {\"type\": \"Textual description of severity\", \"content\": {\"text\": \"moderate\"}}}], \"affected\": [{\"vendor\": \"Apache Software Foundation\", \"product\": \"Apache Camel\", \"versions\": [{\"status\": \"affected\", \"version\": \"4.10.0\", \"lessThan\": \"4.10.2\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"4.8.0\", \"lessThan\": \"4.8.5\", \"versionType\": \"semver\"}, {\"status\": \"affected\", \"version\": \"3.10.0\", \"lessThan\": \"3.22.4\", \"versionType\": \"semver\"}], \"packageName\": \"org.apache.camel:camel\", \"collectionURL\": \"https://repo.maven.apache.org/maven2\", \"defaultStatus\": \"unaffected\"}], \"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\"]}], \"x_generator\": {\"engine\": \"Vulnogram 0.2.0\"}, \"descriptions\": [{\"lang\": \"en\", \"value\": \"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.\\\".\\u00a0\\n\\n\\nMitigation:\\u00a0You can easily work around this in your Camel applications by removing the\\u00a0headers in your Camel routes. There are many ways of doing this, also\\u00a0globally 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.\\\".\", \"supportingMedia\": [{\"type\": \"text/html\", \"value\": \"<p>Bypass/Injection vulnerability in Apache Camel components under particular conditions.</p><p>This issue affects Apache Camel: from 4.10.0 through &lt;= 4.10.1, from 4.8.0 through &lt;= 4.8.4, from 3.10.0 through &lt;= 3.22.3.</p><p>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.</p><div></div><div>This vulnerability is present in Camel's default incoming header filter, that allows an attacker to include Camel specific</div><div>headers that for some Camel components can alter the behaviours such as the camel-bean component, to call another method</div><div>on the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send</div><div>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</div><div><br></div><div>The attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are</div><div>directly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests</div><div>that are send to the Camel application.</div><div><br></div>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.<br><br>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.<br><br><div>In terms of usage of the default header filter strategy the list of components using that is: <br></div><div><div><ul><li>camel-activemq</li><li>camel-activemq6</li><li>camel-amqp</li><li>camel-aws2-sqs</li><li>camel-azure-servicebus</li><li>camel-cxf-rest</li><li>camel-cxf-soap</li><li>camel-http</li><li>camel-jetty</li><li>camel-jms</li><li>camel-kafka</li><li>camel-knative</li><li>camel-mail</li><li>camel-nats</li><li>camel-netty-http</li><li>camel-platform-http</li><li>camel-rest</li><li>camel-sjms</li><li>camel-spring-rabbitmq</li><li>camel-stomp</li><li>camel-tahu</li><li>camel-undertow</li><li>camel-xmpp</li></ul></div></div><div>The vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \\\"Camel\\\", \\\"camel\\\", or \\\"org.apache.camel.\\\".&nbsp;</div><br><div><span style=\\\"background-color: var(--wht);\\\">Mitigation:&nbsp;</span>You can easily work around this in your Camel applications by removing the&nbsp;headers in your Camel routes. There are many ways of doing this, also&nbsp;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.\\\".&nbsp;<br></div><br>\", \"base64\": false}]}], \"problemTypes\": [{\"descriptions\": [{\"lang\": \"en\", \"description\": \"Bypass/Injection\"}]}], \"providerMetadata\": {\"orgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"shortName\": \"apache\", \"dateUpdated\": \"2025-03-17T14:42:57.795Z\"}}}",
         cveMetadata: "{\"cveId\": \"CVE-2025-27636\", \"state\": \"PUBLISHED\", \"dateUpdated\": \"2025-03-17T14:42:57.795Z\", \"dateReserved\": \"2025-03-04T11:56:29.254Z\", \"assignerOrgId\": \"f0158376-9dc2-43b6-827c-5f631a4d8d09\", \"datePublished\": \"2025-03-09T12:09:58.619Z\", \"assignerShortName\": \"apache\"}",
         dataType: "CVE_RECORD",
         dataVersion: "5.1",
      },
   },
}