CVE-2025-27636 apache · camel

Apache Camel: Camel Message Header Injection via Improper Filtering

Vulnerability at a glance

Severity, exploitation likelihood & attack requirements

CVSS v3.1 severity
5.6Medium
EPSS · exploitation likelihood
97.057% Probability within 30 daysPercentile 99.9
EPSS trend
UnavailableNo comparable history
Known exploitation
Not in KEV CISA KEV catalog Absence does not establish safety
Attack vector
NetworkRemotely reachable
Attack complexity
HighMore obstacles to exploitation
Privileges required
NoneNo authentication required
User interaction
NoneNo user action needed
Exploit availability & maturity
Not scored Exploit reference available No explicit exploit maturity assessment View exploit evidence
How to read the colors & trend
Higher exposureElevatedModerateLower exposureUnknown / unassessed

CVSS colors follow its reported severity. Attack-factor colors describe each requirement, not an overall risk rating. Gray also covers absence from KEV; absence does not establish safety.

EPSS display bands: below 1% blue, 1–10% amber, 10–50% orange, 50% and above red. These are presentation bands, not FIRST severity categories. The trend compares daily EPSS probabilities, not percentile ranks; “pp” means percentage points. The sparkline shows relative movement, with its vertical scale fitted to the observed scores.

Already protected by existing Atomicorp rules No new CVE-specific rule required.

Atomicorp ModSecurity protection

Protected by Atomicorp rules

Atomicorp ModSecurity rules block attacks exploiting this vulnerability. Keep your rules current.

By targeting underlying attack techniques and CWE weakness classes, existing rules can protect against newly disclosed vulnerabilities. Rule changes are regression-tested against attack and false-positive corpora.

1 rule identified Verified 2026-11-22 View rules & research details →

WAF protection does not change the CVSS or EPSS score. Keep your software patched and your Atomicorp rules current.

CISA SSVC assessment

CISA ADP · Assessed 2025-10-22 · SSVC 2.0.3

Exploitation
Proof-of-concept
Automatable
No
Technical Impact
Partial

Stakeholder-Specific Vulnerability Categorization records CISA’s assessment of exploitation, automation, and technical impact. “None reported” reflects the assessment date; it does not establish that no exploit exists. View SSVC source details.

On this page

CVE Details

  • Protection status: Protected by Atomicorp rules · About protection statuses
  • CVE: CVE-2025-27636
  • Name: Apache Camel: Camel Message Header Injection via Improper Filtering
  • Severity: Medium
  • CVSS: 5.6 (v3.1) (Medium)
  • CVSS version: 3.1
  • CVSS source: CISA ADP
  • CVSS vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
    • Attack vector: Network
    • Attack complexity: High
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: Low
    • Integrity impact: Low
    • Availability impact: Low
  • CWE: CWE-178 — Improper Handling of Case Sensitivity
  • Vendor: apache
  • Vulnerable product: camel
  • CVE published: 2025-03-09
  • CVE last modified: 2026-06-17
  • Affected versions (NVD configurations):
    • camel: >= 3.10.0, < 3.22.4
    • camel: >= 4.8.0, < 4.8.5
    • camel: >= 4.10.0, < 4.10.2
  • EPSS: 0.9706; 99.9th percentile as of 2026-11-21 (FIRST (opens in a new tab) )
  • Latest Update: 2026-11-22
  • Selected Rule IDs observed: 340009
  • Matching rules: 1; rules with blocking actions: 1
  • Would-block Rule IDs: 340009
  • Request surfaces inspected: JSON request data, Request arguments, Request headers, SOAP request data
Technical vulnerability details · CVSS assessments, exploit evidence & CPE data

CVSS assessments

CVSS v3.1 · CISA ADP

  • Base score: 5.6
  • Base severity: MEDIUM
  • Exploitability subscore: 2.2
  • Impact subscore: 3.4
  • Assessment type: Secondary
  • Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
  • Full vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:L
    • Attack vector: Network
    • Attack complexity: High
    • Privileges required: None
    • User interaction: None
    • Scope: Unchanged
    • Confidentiality impact: Low
    • Integrity impact: Low
    • Availability impact: Low
  • Exploit maturity: Not scored

Exploitability and impact subscores describe the vulnerability’s technical characteristics. Exploit maturity describes the reported state of exploitation; these are separate measures.

Assessment source: NVD record (opens in a new tab) · CVE record (opens in a new tab)

CISA SSVC assessments

These are CISA’s published decision points at the assessment time. They are not a complete organization-specific prioritization decision.

  • Provider: CISA ADP
  • Provider identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
  • SSVC version: 2.0.3
  • Role: CISA Coordinator
  • Assessment timestamp: 2025-10-22T03:55:18.536426Z
  • Exploitation: poc
  • Automatable: no
  • Technical Impact: partial
  • Source: CISA ADP in the CVE record (opens in a new tab)

Exploit references

The CVE source data tags these references as exploits. A reference alone does not establish reliability or active exploitation.

Vulnerable CPE configurations

  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*
    • Version start (inclusive): 3.10.0
    • Version end (exclusive): 3.22.4
    • NVD match criteria ID: F955C7FA-20EE-44FC-BB7F-2734A731A9DC
  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*
    • Version start (inclusive): 4.8.0
    • Version end (exclusive): 4.8.5
    • NVD match criteria ID: 15914F75-761B-40AD-8489-EA92699F3741
  • cpe:2.3:a:apache:camel:*:*:*:*:*:*:*:*
    • Version start (inclusive): 4.10.0
    • Version end (exclusive): 4.10.2
    • NVD match criteria ID: DB496A7D-7E5D-48DA-B49F-4494B7369026

Vulnerability Description

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.”.

  1. Maintain the observed Atomicorp protections. Keep your Atomicorp commercial rules current and confirm that the selected observed rules (340009 ) have not been locally disabled. Atomicorp commercial rules are enabled by default. If you use Atomic WAF, review the applicable policy and rule settings.

  2. Apply the vendor’s remediation. WAF protection is defense in depth and does not replace upgrading or following the affected vendor’s guidance.

    • Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.10.2.
    • Affected versions: Apache Software Foundation Apache Camel versions earlier than 4.8.5.
    • Affected versions: Apache Software Foundation Apache Camel versions earlier than 3.22.4.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.10.2 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 4.8.5 or later.
    • Recommended upgrade: Upgrade Apache Software Foundation Apache Camel to 3.22.4 or later.
    • The CVE record does not include written upgrade or workaround instructions, but it does publish the following patch or mitigation reference:
  3. Validate after changes. Confirm rule updates are current, review WAF events for the affected application, and test application behavior after vendor upgrades, mitigations, or local policy changes.

Research Notes

Atomicorp WAF protections are designed around attack techniques and exploit behaviors, allowing existing protections to apply across multiple vulnerabilities without requiring a unique rule for every CVE.

Public Vulnerability References

Test or Research Source

Research Note Context

This research note documents exploit-technique analysis associated with this vulnerability and references Atomicorp WAF protections observed during engineering review, testing, or validation activities.

Atomicorp security controls are generally designed to identify and mitigate attack techniques and exploit behaviors rather than individual CVE identifiers. As a result, protections developed for one vulnerability may also apply to related attack variants and future vulnerabilities using similar techniques.

Learn More

Atomicorp develops commercially supported security technologies for web applications, servers, endpoints, workloads, and legacy enterprise platforms.

Organizations interested in protecting systems against exploit techniques associated with vulnerabilities such as this one can learn more about:

  • Atomic ModSecurity Rules: commercially maintained WAF rules for ModSecurity deployments, including protections for web attacks, bots, scanners, malware, exploitation attempts, and emerging vulnerability classes.
  • Atomic WAF: an enterprise web application firewall with Atomicorp rules, centralized management, reporting, authentication controls, and operational tooling.
  • Atomic ModSecurity Integrator: a special licensing option for MSPs, MSSPs, OEMs, VARs, reverse proxy providers, and other integrators who want to incorporate Atomicorp ModSecurity rule technology into their own products or services.
  • Atomic OSSEC: an enterprise OSSEC-based intrusion detection, compliance, and security monitoring platform.
  • Atomic Protector: workload protection for Linux, web, cloud, data center, and hybrid environments.

For additional information, product evaluations, or technical discussions, visit https://www.atomicorp.com/ or https://modsecurity.io/ (opens in a new tab) .