CVE-2025-27636 (GCVE-0-2025-27636)

Vulnerability from cvelistv5 – Published: 2025-03-09 12:09 – Updated: 2026-02-26 19:09
VLAI
Title
Apache Camel: Camel Message Header Injection via Improper Filtering
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.".
Severity
5.6 (Medium)
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
SSVC
Exploitation: poc Automatable: no Technical Impact: partial
CISA Coordinator (v2.0.3)
CWE
  • Bypass/Injection
  • CWE-178 - Improper Handling of Case Sensitivity
Assigner
References
Impacted products
Vendor Product Version
Apache Software Foundation Apache Camel Affected: 4.10.0 , < 4.10.2 (semver)
Affected: 4.8.0 , < 4.8.5 (semver)
Affected: 3.10.0 , < 3.22.4 (semver)
Create a notification for this product.
Credits
Mark Thorson
Show details on NVD website
To clipboard 

{
  "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-10-22T03:55:18.536426Z",
                "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": "2026-02-26T19:09:44.229Z",
          "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": "\u003cp\u003eBypass/Injection vulnerability in Apache Camel components under particular conditions.\u003c/p\u003e\u003cp\u003eThis issue affects Apache Camel: from 4.10.0 through \u0026lt;= 4.10.1, from 4.8.0 through \u0026lt;= 4.8.4, from 3.10.0 through \u0026lt;= 3.22.3.\u003c/p\u003e\u003cp\u003eUsers 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.\u003c/p\u003e\u003cdiv\u003e\u003c/div\u003e\u003cdiv\u003eThis vulnerability is present in Camel\u0027s default incoming header filter, that allows an attacker to include Camel specific\u003c/div\u003e\u003cdiv\u003eheaders that for some Camel components can alter the behaviours such as the camel-bean component, to call another method\u003c/div\u003e\u003cdiv\u003eon the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send\u003c/div\u003e\u003cdiv\u003ethe 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\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003e\u003cdiv\u003eThe attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are\u003c/div\u003e\u003cdiv\u003edirectly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests\u003c/div\u003e\u003cdiv\u003ethat are send to the Camel application.\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003eAll 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.\u003cbr\u003e\u003cbr\u003eIn 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.\u003cbr\u003e\u003cbr\u003e\u003cdiv\u003eIn terms of usage of the default header filter strategy the list of components using that is: \u003cbr\u003e\u003c/div\u003e\u003cdiv\u003e\u003cdiv\u003e\u003cul\u003e\u003cli\u003ecamel-activemq\u003c/li\u003e\u003cli\u003ecamel-activemq6\u003c/li\u003e\u003cli\u003ecamel-amqp\u003c/li\u003e\u003cli\u003ecamel-aws2-sqs\u003c/li\u003e\u003cli\u003ecamel-azure-servicebus\u003c/li\u003e\u003cli\u003ecamel-cxf-rest\u003c/li\u003e\u003cli\u003ecamel-cxf-soap\u003c/li\u003e\u003cli\u003ecamel-http\u003c/li\u003e\u003cli\u003ecamel-jetty\u003c/li\u003e\u003cli\u003ecamel-jms\u003c/li\u003e\u003cli\u003ecamel-kafka\u003c/li\u003e\u003cli\u003ecamel-knative\u003c/li\u003e\u003cli\u003ecamel-mail\u003c/li\u003e\u003cli\u003ecamel-nats\u003c/li\u003e\u003cli\u003ecamel-netty-http\u003c/li\u003e\u003cli\u003ecamel-platform-http\u003c/li\u003e\u003cli\u003ecamel-rest\u003c/li\u003e\u003cli\u003ecamel-sjms\u003c/li\u003e\u003cli\u003ecamel-spring-rabbitmq\u003c/li\u003e\u003cli\u003ecamel-stomp\u003c/li\u003e\u003cli\u003ecamel-tahu\u003c/li\u003e\u003cli\u003ecamel-undertow\u003c/li\u003e\u003cli\u003ecamel-xmpp\u003c/li\u003e\u003c/ul\u003e\u003c/div\u003e\u003c/div\u003e\u003cdiv\u003eThe vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \"Camel\", \"camel\", or \"org.apache.camel.\".\u0026nbsp;\u003c/div\u003e\u003cbr\u003e\u003cdiv\u003e\u003cspan style=\"background-color: var(--wht);\"\u003eMitigation:\u0026nbsp;\u003c/span\u003eYou can easily work around this in your Camel applications by removing the\u0026nbsp;headers in your Camel routes. There are many ways of doing this, also\u0026nbsp;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.\".\u0026nbsp;\u003cbr\u003e\u003c/div\u003e\u003cbr\u003e"
            }
          ],
          "value": "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\n\n\nThis vulnerability is present in Camel\u0027s 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.\"."
        }
      ],
      "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": "2026-02-26T19:09:44.229Z",
    "state": "PUBLISHED"
  },
  "dataType": "CVE_RECORD",
  "dataVersion": "5.2",
  "vulnerability-lookup:meta": {
    "epss": {
      "cve": "CVE-2025-27636",
      "date": "2026-06-17",
      "epss": "0.79817",
      "percentile": "0.99559"
    },
    "nvd": "{\"cve\":{\"id\":\"CVE-2025-27636\",\"sourceIdentifier\":\"security@apache.org\",\"published\":\"2025-03-09T13:15:34.403\",\"lastModified\":\"2025-06-23T18:54:52.400\",\"vulnStatus\":\"Analyzed\",\"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 \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\\n\\n\\nThis vulnerability is present in Camel\u0027s 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.\\\".\"},{\"lang\":\"es\",\"value\":\"Vulnerabilidad de bypass/inyecci\u00f3n en el componente Apache Camel-Bean en determinadas condiciones. Este problema afecta a Apache Camel: desde la versi\u00f3n 4.10.0 hasta la \u0026lt;= 4.10.1, desde la versi\u00f3n 4.8.0 hasta la \u0026lt;= 4.8.4, desde la versi\u00f3n 3.10.0 hasta la \u0026lt;= 3.22.3. Se recomienda a los usuarios que actualicen a la versi\u00f3n 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\u00e1 presente en la siguiente situaci\u00f3n. El usuario est\u00e1 utilizando uno de los siguientes servidores HTTP a trav\u00e9s 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\u00e1 a un productor de camel-bean. Por lo tanto, SOLO el componente camel-bean est\u00e1 afectado. En particular: * La invocaci\u00f3n 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\u00e1s de 1 m\u00e9todo implementado. En estas condiciones, un atacante podr\u00eda falsificar un nombre de encabezado de Camel y hacer que el componente bean invoque otros m\u00e9todos 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\u00f3n: puedes solucionar esto f\u00e1cilmente en tus aplicaciones Camel eliminando los encabezados en tus rutas Camel. Hay muchas formas de hacer esto, tambi\u00e9n 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\"}]}],\"configurations\":[{\"nodes\":[{\"operator\":\"OR\",\"negate\":false,\"cpeMatch\":[{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"3.10.0\",\"versionEndExcluding\":\"3.22.4\",\"matchCriteriaId\":\"F955C7FA-20EE-44FC-BB7F-2734A731A9DC\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"4.8.0\",\"versionEndExcluding\":\"4.8.5\",\"matchCriteriaId\":\"15914F75-761B-40AD-8489-EA92699F3741\"},{\"vulnerable\":true,\"criteria\":\"cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*\",\"versionStartIncluding\":\"4.10.0\",\"versionEndExcluding\":\"4.10.2\",\"matchCriteriaId\":\"DB496A7D-7E5D-48DA-B49F-4494B7369026\"}]}]}],\"references\":[{\"url\":\"https://camel.apache.org/security/CVE-2025-27636.html\",\"source\":\"security@apache.org\",\"tags\":[\"Vendor Advisory\"]},{\"url\":\"https://issues.apache.org/jira/browse/CAMEL-21828\",\"source\":\"security@apache.org\",\"tags\":[\"Issue Tracking\",\"Patch\"]},{\"url\":\"https://lists.apache.org/thread/l3zcg3vts88bmc7w8172wkgw610y693z\",\"source\":\"security@apache.org\",\"tags\":[\"Mailing List\",\"Vendor Advisory\"]},{\"url\":\"http://www.openwall.com/lists/oss-security/2025/03/09/1\",\"source\":\"af854a3a-2127-422b-91ae-364da2661108\",\"tags\":[\"Mailing List\",\"Third Party Advisory\"]},{\"url\":\"https://camel.apache.org/security/CVE-2025-27636.txt.asc\",\"source\":\"134c704f-9b21-4f2e-91b3-4a467353bcc0\",\"tags\":[\"Exploit\"]},{\"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\",\"tags\":[\"Product\"]}]}}",
    "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-10-22T03:55:18.536426Z\"}}}], \"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 \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\\n\\n\\nThis vulnerability is present in Camel\u0027s 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\": \"\u003cp\u003eBypass/Injection vulnerability in Apache Camel components under particular conditions.\u003c/p\u003e\u003cp\u003eThis issue affects Apache Camel: from 4.10.0 through \u0026lt;= 4.10.1, from 4.8.0 through \u0026lt;= 4.8.4, from 3.10.0 through \u0026lt;= 3.22.3.\u003c/p\u003e\u003cp\u003eUsers 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.\u003c/p\u003e\u003cdiv\u003e\u003c/div\u003e\u003cdiv\u003eThis vulnerability is present in Camel\u0027s default incoming header filter, that allows an attacker to include Camel specific\u003c/div\u003e\u003cdiv\u003eheaders that for some Camel components can alter the behaviours such as the camel-bean component, to call another method\u003c/div\u003e\u003cdiv\u003eon the bean, than was coded in the application. In the camel-jms component, then a malicious header can be used to send\u003c/div\u003e\u003cdiv\u003ethe 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\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003e\u003cdiv\u003eThe attacker would need to inject custom headers, such as HTTP protocols. So if you have Camel applications that are\u003c/div\u003e\u003cdiv\u003edirectly connected to the internet via HTTP, then an attacker could include malicious HTTP headers in the HTTP requests\u003c/div\u003e\u003cdiv\u003ethat are send to the Camel application.\u003c/div\u003e\u003cdiv\u003e\u003cbr\u003e\u003c/div\u003eAll 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.\u003cbr\u003e\u003cbr\u003eIn 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.\u003cbr\u003e\u003cbr\u003e\u003cdiv\u003eIn terms of usage of the default header filter strategy the list of components using that is: \u003cbr\u003e\u003c/div\u003e\u003cdiv\u003e\u003cdiv\u003e\u003cul\u003e\u003cli\u003ecamel-activemq\u003c/li\u003e\u003cli\u003ecamel-activemq6\u003c/li\u003e\u003cli\u003ecamel-amqp\u003c/li\u003e\u003cli\u003ecamel-aws2-sqs\u003c/li\u003e\u003cli\u003ecamel-azure-servicebus\u003c/li\u003e\u003cli\u003ecamel-cxf-rest\u003c/li\u003e\u003cli\u003ecamel-cxf-soap\u003c/li\u003e\u003cli\u003ecamel-http\u003c/li\u003e\u003cli\u003ecamel-jetty\u003c/li\u003e\u003cli\u003ecamel-jms\u003c/li\u003e\u003cli\u003ecamel-kafka\u003c/li\u003e\u003cli\u003ecamel-knative\u003c/li\u003e\u003cli\u003ecamel-mail\u003c/li\u003e\u003cli\u003ecamel-nats\u003c/li\u003e\u003cli\u003ecamel-netty-http\u003c/li\u003e\u003cli\u003ecamel-platform-http\u003c/li\u003e\u003cli\u003ecamel-rest\u003c/li\u003e\u003cli\u003ecamel-sjms\u003c/li\u003e\u003cli\u003ecamel-spring-rabbitmq\u003c/li\u003e\u003cli\u003ecamel-stomp\u003c/li\u003e\u003cli\u003ecamel-tahu\u003c/li\u003e\u003cli\u003ecamel-undertow\u003c/li\u003e\u003cli\u003ecamel-xmpp\u003c/li\u003e\u003c/ul\u003e\u003c/div\u003e\u003c/div\u003e\u003cdiv\u003eThe vulnerability arises due to a bug in the default filtering mechanism that only blocks headers starting with \\\"Camel\\\", \\\"camel\\\", or \\\"org.apache.camel.\\\".\u0026nbsp;\u003c/div\u003e\u003cbr\u003e\u003cdiv\u003e\u003cspan style=\\\"background-color: var(--wht);\\\"\u003eMitigation:\u0026nbsp;\u003c/span\u003eYou can easily work around this in your Camel applications by removing the\u0026nbsp;headers in your Camel routes. There are many ways of doing this, also\u0026nbsp;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.\\\".\u0026nbsp;\u003cbr\u003e\u003c/div\u003e\u003cbr\u003e\", \"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\": \"2026-02-26T19:09:44.229Z\", \"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.2"
    }
  }
}


Log in or create an account to share your comment.




Tags
Taxonomy of the tags.





Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.


Detection rules are retrieved from Rulezet.