Skip to content

Apache Camel has an incomplete fix for CVE-2025-27636

Critical severity GitHub Reviewed Published Apr 27, 2026 to the GitHub Advisory Database • Updated May 22, 2026

Package

maven org.apache.camel:camel-coap (Maven)

Affected versions

>= 3.0.0, < 4.14.6
>= 4.15.0, < 4.18.2
>= 4.19.0, < 4.20.0

Patched versions

4.14.6
4.18.2
4.20.0
maven org.apache.camel:camel-google-pubsub (Maven)
>= 3.0.0, < 4.14.6
>= 4.15.0, < 4.18.2
>= 4.19.0, < 4.20.0
4.14.6
4.18.2
4.20.0
maven org.apache.camel:camel-jms (Maven)
>= 3.0.0, < 4.14.6
>= 4.15.0, < 4.18.2
>= 4.19.0, < 4.20.0
4.14.6
4.18.2
4.20.0
maven org.apache.camel:camel-sjms (Maven)
>= 3.0.0, < 4.14.6
>= 4.15.0, < 4.18.2
>= 4.19.0, < 4.20.0
4.14.6
4.18.2
4.20.0

Description

The fix for CVE-2025-27636 added setLowerCase(true) to HttpHeaderFilterStrategy so that case-variant header names such as 'CAmelExecCommandExecutable' are filtered out alongside 'CamelExecCommandExecutable'. The same setLowerCase(true) call was not applied to five non-HTTP HeaderFilterStrategy implementations: JmsHeaderFilterStrategy and ClassicJmsHeaderFilterStrategy in camel-jms, SjmsHeaderFilterStrategy in camel-sjms, CoAPHeaderFilterStrategy in camel-coap, and GooglePubsubHeaderFilterStrategy in camel-google-pubsub. Because those strategies use case-sensitive String.startsWith('Camel'/'camel') filtering while the Camel Exchange stores headers in a case-insensitive map, an attacker with JMS (or equivalent) producer access to the broker consumed by a Camel route can inject case-variant Camel internal headers, which are then resolved by downstream components such as camel-exec and camel-file using their canonical casing. This enables remote code execution and arbitrary file write on routes that forward JMS messages to header-driven components.

This issue affects Apache Camel: from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.2, from 4.19.0 before 4.20.0.

Users are recommended to upgrade to version 4.20.0, which fixes the issue. If users are on the 4.14.x LTS releases stream, then they are suggested to upgrade to 4.14.6. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.2.

References

Published by the National Vulnerability Database Apr 27, 2026
Published to the GitHub Advisory Database Apr 27, 2026
Reviewed May 22, 2026
Last updated May 22, 2026

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(54th percentile)

Weaknesses

Improper Handling of Case Sensitivity

The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results. Learn more on MITRE.

CVE ID

CVE-2026-40453

GHSA ID

GHSA-jg2m-9x48-3gvj

Source code

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.