Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 1.89% for the current model date.
BlackTreeCVE IntelligenceFull vulnerability report · 2026
CVE-2026-40453High confidence
Apache Camel JMS, Apache Camel CoAP, Apache Camel Google PubSub: Incomplete fix for CVE-2025-27636 in non-HTTP HeaderFilterStrategies (camel-jms, camel-sjms, camel-coap, camel-google-pubsub) allows case-variant header injection
Apache Software Foundation · Apache Camel JMS
9.9CriticalCVSS 3.1
Patch only the product branches with a verified fix
Fix availability varies by productCritical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 8 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
R
Open reassessment dashboard →Operational reassessment
Published severity in operational context
Published severityCritical→Operational priority:Critical, unchanged from published severity.unchanged
Compensating controls
- Validate the affected product branch and deploy the verified fixed release.
- Restrict the affected network interface to trusted sources where business-safe.
- Monitor vendor guidance and exploitation sources for a material change.
Verification
- Confirm that the asset runs Apache Software Foundation Apache Camel JMS and falls inside the recorded affected range.
- Verify the installed build against the product-specific fixed version after deployment.
- Validate exposure, authentication requirements and compensating controls in the actual environment.
- Reopen this reassessment when CVSS, KEV, EPSS, exploit evidence or remediation changes.
Remediation availability differs by product scope
Verified remediation exists for at least one product or source, but 8 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
- Red Hat Product Security: 8 affected or under-investigation product states without a fixed product state in the same current advisory
Open-source package ranges24 source-attributed ranges
These OSV and GitHub advisory ranges apply only to the named package and ecosystem. A listed fixed version is not a universal product patch or proof that an update is installed.
| Ecosystem and package | Affected range | First fixed version | Evidence |
|---|---|---|---|
| Mavenorg.apache.camel:camel-coap | ECOSYSTEM: introduced 3.0.0; fixed 4.14.6 | 4.14.6 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-coap | ECOSYSTEM: introduced 4.15.0; fixed 4.18.2 | 4.18.2 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-coap | ECOSYSTEM: introduced 4.19.0; fixed 4.20.0 | 4.20.0 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-google-pubsub | ECOSYSTEM: introduced 3.0.0; fixed 4.14.6 | 4.14.6 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-google-pubsub | ECOSYSTEM: introduced 4.15.0; fixed 4.18.2 | 4.18.2 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-google-pubsub | ECOSYSTEM: introduced 4.19.0; fixed 4.20.0 | 4.20.0 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-jms | ECOSYSTEM: introduced 3.0.0; fixed 4.14.6 | 4.14.6 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-jms | ECOSYSTEM: introduced 4.15.0; fixed 4.18.2 | 4.18.2 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-jms | ECOSYSTEM: introduced 4.19.0; fixed 4.20.0 | 4.20.0 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-sjms | ECOSYSTEM: introduced 3.0.0; fixed 4.14.6 | 4.14.6 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-sjms | ECOSYSTEM: introduced 4.15.0; fixed 4.18.2 | 4.18.2 | OSV record ↗aggregator derived · 5 Oct 2026 |
| Mavenorg.apache.camel:camel-sjms | ECOSYSTEM: introduced 4.19.0; fixed 4.20.0 | 4.20.0 | OSV record ↗aggregator derived · 5 Oct 2026 |
| mavenorg.apache.camel:camel-coap | >= 3.0.0, < 4.14.6 | 4.14.6 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-coap | >= 4.15.0, < 4.18.2 | 4.18.2 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-coap | >= 4.19.0, < 4.20.0 | 4.20.0 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-google-pubsub | >= 3.0.0, < 4.14.6 | 4.14.6 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-google-pubsub | >= 4.15.0, < 4.18.2 | 4.18.2 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-google-pubsub | >= 4.19.0, < 4.20.0 | 4.20.0 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-jms | >= 3.0.0, < 4.14.6 | 4.14.6 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-jms | >= 4.15.0, < 4.18.2 | 4.18.2 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-jms | >= 4.19.0, < 4.20.0 | 4.20.0 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-sjms | >= 3.0.0, < 4.14.6 | 4.14.6 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-sjms | >= 4.15.0, < 4.18.2 | 4.18.2 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
| mavenorg.apache.camel:camel-sjms | >= 4.19.0, < 4.20.0 | 4.20.0 | GitHub advisory ↗github reviewed aggregator · 5 Oct 2026 |
Direct vendor intelligence
1 currentAuthoritative vendor CSAF and VEX advisories
Structured product status and remediation from the issuing vendor. Product-state explanations are always visible; large lists can be searched or downloaded.
CVE-2026-40453 · CSAF 2.0 · revision 3 · finalRed Hat Product SecurityApache Camel: org.apache.camel: Apache Camel: Remote Code Execution and Arbitrary File Write via case-variant header injection
The vendor explicitly identifies these products as affected by this CVE.
- camel-google-pubsub as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- camel-jms as a component of Red Hat build of Apache Camel 4 for Quarkus 3
- Summary
- A flaw was found in Apache Camel. A remote attacker with Java Message Service (JMS) producer access could exploit a vulnerability in how certain header filter strategies process case-variant internal headers. This discrepancy, where filtering is case-sensitive but header processing is not, allows for the injection of malicious headers. Consequently, this could lead to remote code execution and arbitrary file write on affected Camel routes.
- Remediation
- Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
Critical technical severity; prioritise exposed affected systems while verifying vendor guidance. Verified remediation exists for at least one product or source, but 8 structured product or package states remain unresolved. Apply remediation only to the exact product branch confirmed by its source.
Fix availability varies by product01
What, why and how
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.
What
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.
Why
The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
What
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.
Why
The product does not properly account for differences in case sensitivity when accessing or determining the properties of a resource, leading to inconsistent results.
How
An attacker operating through a network path may attempt exploitation with low privileges. If successful, the issue may execute code or commands in the affected security context.
02
Exploit reality and attack path
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
Observed exploitation No confirmed evidence
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
Public PoC / exploit material None recorded
?
Confirmed exploitation and public exploit material are separate signals. Attacks can occur without public proof-of-concept or exploit code.No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
- Likely attack path
- a network path → Improper Handling of Case Sensitivity → execute code or commands in the affected security context
- Attack surface
- Network
- Privileges required
- Low: a basic authenticated account is required
- User interaction
- None
- Attack complexity
- Low: no specialised conditions are recorded
- Security boundary
- Changed: exploitation can affect a different security authority
- Weakness
?
CWE means Common Weakness Enumeration: a standard category for the underlying weakness. - CWE-178 ↗
CWE-178: 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.
- CVSS vector
?
CVSS means Common Vulnerability Scoring System. The vector records the metric values used to calculate technical severity. CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
AVNetworkAttack vector: The vulnerable component can be reached over a network.ACLowAttack complexity: No specialised conditions are required beyond attacker-controlled input.PRLowPrivileges required: The attacker needs basic user-level privileges.UINoneUser interaction: No action by another user is required.SChangedScope: The attack can affect a component governed by a different security authority.CHighConfidentiality impact: A successful attack can cause a major loss.IHighIntegrity impact: A successful attack can cause a major loss.AHighAvailability impact: A successful attack can cause a major loss.- Post-exploitation / living off the land
- After compromise, an attacker may use built-in shells, scripting engines, scheduled tasks and native network utilities for discovery, persistence or movement. This is a plausible LoTL path, not evidence that it has occurred for every attack.
03
Patch and workaround
Operational remediation based on structured source evidence.
- Status
?
Patch availability is based on structured fixed-version fields and authoritative update references. If no fix is verified, check the vendor advisory before making a change. - Fix availability varies by product
- Affected
- Action
- Use the product-specific evidence above. Patch only products with a verified fixed release, and keep every affected or under-investigation state without a matching fix in the remediation queue.
- Workaround
- No verified workaround is recorded. If business-safe, reduce exposure to the affected interface and allow only trusted sources until authoritative guidance is available.
04
Evidence and provenance
Published 27 Apr 2026 · Last source change 15 Jul 2026, 01:01 UTC · CWE-178 · Improper Handling of Case Sensitivity
CVE recordCVE.org · 5.2
CVSS sourceCISA ADP
EPSS source FIRST · tracked since 2026-08-14
?
The date BlackTree first stored a score for this CVE from the daily FIRST EPSS feed.European sourceENISA EUVD · EUVD-2026-25791
Product sourceVendor CSAF · Red Hat Product Security
Remediation sourceVendor CSAF · Red Hat Product Security
CWE sourceCNA
NVD statusNVD modified after enrichment
Core structured fields are present and their contributing authorities are shown above.
Material change intelligence
View recent updates ↗What changed after publication
- Affected versionsThe structured affected or fixed version information changed.Red Hat Product Security ↗
- Before
- 3.0.0 < 4.14.6; 4.15.0 < 4.18.2; 4.19.0 < 4.20.0 · Fixed: No fixed version is explicitly recorded in the structured CVE data.
- After
- 3.0.0 < 4.14.6; 4.15.0 < 4.18.2; 4.19.0 < 4.20.0 · Fixed: Before applying this update, make sure all previously released errata relevant to your system have been applied. For details on how to apply this update, refer to: https://access.redhat.com/articles/11258
- Remediation statusRemediation status changed from Awaiting fix to Patch available.Red Hat Product Security ↗
- Before
- Awaiting fix
- After
- Patch available
CVE published
Fixed release recorded from official guidance
Technical terms and abbreviations used in this report
- CVE
- Common Vulnerabilities and Exposures: the public identifier for one disclosed vulnerability.
- CVSS
- Common Vulnerability Scoring System: a technical severity framework; it is not patching priority by itself.
- EPSS
- Exploit Prediction Scoring System: FIRST's estimate of the probability that exploitation activity will be observed in the next 30 days; it is a forecast, not confirmation.
- CWE
- Common Weakness Enumeration: the standard category describing the underlying software or hardware weakness.
- CNA
- CVE Numbering Authority: an organisation authorised to assign and publish CVE records.
- CISA ADP
- Cybersecurity and Infrastructure Security Agency Authorized Data Publisher: structured enrichment added to a CVE record.
- NVD
- National Vulnerability Database: NIST's enrichment service for CVE records.
- CERT / CSIRT
- A computer security incident response team that publishes warnings or coordinates incident response.
- PoC
- Proof of concept: public material that demonstrates or helps reproduce exploitation.
- CSAF
- Common Security Advisory Framework: a machine-readable format for security advisories.
- LoTL
- Living off the land: abuse of legitimate tools or system functions during an attack.