Skip to content
Heist/ feed
Back to feed
Medium

Apache Camel: Camel Message Header Injection via Improper Filtering

Type: advisorySources: OSV

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 u

Products
Not specified
Affected versions
Not specified
Fixed versions
Not specified
CVEs
CVE-2025-27636
Confirmed fixed CVEs
Not specified
Updated in this feed
5 Nov 2026, 01:44 UTC · Revision 1

Source evidence

Apache Camel: Camel Message Header Injection via Improper Filtering

core-osv · Original source

Published 9 Mar 2025, 12:09 UTC

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 u

osv:CVE-2025-27636
Complete source record
{
  "id": "070ee17d9e31ae84caef2d7da94557d1dfd700c0b11ca806897ff7c59bd7a4d6",
  "url": "https://osv.dev/vulnerability/CVE-2025-27636",
  "method": "structured",
  "payload": {
    "kind": "advisory",
    "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 u",
    "evidence": "osv:CVE-2025-27636",
    "products": [],
    "severity": "medium",
    "structured": {
      "id": "CVE-2025-27636",
      "aliases": [
        "CVE-2025-27636",
        "GHSA-2c2h-2855-mf97"
      ],
      "metrics": [
        {
          "type": "CVSS_V3",
          "score": "CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L"
        }
      ],
      "affected": [
        {
          "ranges": [
            {
              "repo": "https://github.com/apache/camel",
              "type": "GIT",
              "events": [
                {
                  "introduced": "545627aaf16cc13ce72c09e2e2b10d94f7bc8f98"
                },
                {
                  "fixed": "8f002c031c008470a0703ae9aaba206a96b1dbf9"
                },
                {
                  "introduced": "071f95d5647b8597ca1c4ae6201b3442f87d120d"
                },
                {
                  "fixed": "63b0ee312c7e42e8a154447d80b939b0e533aa7b"
                },
                {
                  "introduced": "6f00e4749db83b2f8b797b79e7cf9c4ace314ba9"
                },
                {
                  "fixed": "8a56ec5eb26f4ddd033d10690a13cb76cbe699d5"
                }
              ],
              "database_specific": {
                "extracted_events": [
                  {
                    "cpe": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "3.10.0"
                      },
                      {
                        "fixed": "3.22.4"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "cpe": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "4.8.0"
                      },
                      {
                        "fixed": "4.8.5"
                      }
                    ],
                    "source": "CPE_RANGE"
                  },
                  {
                    "cpe": "cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*",
                    "range": [
                      {
                        "introduced": "4.10.0"
                      },
                      {
                        "fixed": "4.10.2"
                      }
                    ],
                    "source": "CPE_RANGE"
                  }
                ]
              }
            }
          ],
          "database_specific": {
            "source": "https://storage.googleapis.com/cve-osv-conversion/osv-output/CVE-2025-27636.json"
          }
        }
      ],
      "modified": "2026-10-28T02:30:41.375777931Z",
      "provider": "osv",
      "references": [
        "https://repo.maven.apache.org/maven2",
        "https://camel.apache.org/security/CVE-2025-27636.html",
        "https://camel.apache.org/security/CVE-2025-27636.txt.asc",
        "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/27xxx/CVE-2025-27636.json",
        "https://lists.apache.org/thread/l3zcg3vts88bmc7w8172wkgw610y693z",
        "https://nvd.nist.gov/vuln/detail/CVE-2025-27636",
        "https://issues.apache.org/jira/browse/CAMEL-21828",
        "https://github.com/akamai/CVE-2025-27636-Apache-Camel-PoC/blob/main/src/main/java/com/example/camel/VulnerableCamel.java"
      ],
      "provider_metadata": {
        "cna_assigner": "apache",
        "unresolved_ranges": [
          {
            "extracted_events": [
              {
                "range": [
                  {
                    "introduced": "4.10.0"
                  },
                  {
                    "fixed": "4.10.2"
                  },
                  {
                    "introduced": "4.8.0"
                  },
                  {
                    "fixed": "4.8.5"
                  },
                  {
                    "introduced": "3.10.0"
                  },
                  {
                    "fixed": "3.22.4"
                  }
                ],
                "source": "AFFECTED_FIELD",
                "strategy": "StandardRange"
              }
            ]
          }
        ],
        "osv_generated_from": "https://github.com/CVEProject/cvelistV5/tree/main/cves/2025/27xxx/CVE-2025-27636.json"
      }
    },
    "related_cves": [
      {
        "value": "CVE-2025-27636",
        "evidence": "/id"
      }
    ],
    "security_relevant": true,
    "severity_evidence": "/severity/0/score"
  },
  "source_id": "core-osv",
  "document_id": 509171,
  "published_at": "2025-03-09T12:09:58.619+00:00"
}