Answer in brief
CVE-2026-40453 records a Critical severity (CVSS 9.9) vulnerability in 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. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/Apache Camel CoAP (generic), Apache Software Foundation/Apache Camel Google PubSub (generic), Apache Software Foundation/Apache Camel JMS (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
Answer in brief
CVE-2026-40453 records a Critical severity (CVSS 9.9) vulnerability in 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. The current sources do not mark it as known exploited. The current feed maps Apache Software Foundation/Apache Camel CoAP (generic), Apache Software Foundation/Apache Camel Google PubSub (generic), Apache Software Foundation/Apache Camel JMS (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/Apache Camel CoAP (generic), Apache Software Foundation/Apache Camel Google PubSub (generic), Apache Software Foundation/Apache Camel JMS (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/Apache Camel CoAPgeneric | >=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 |
| Apache Software Foundation/Apache Camel Google PubSubgeneric | >=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 |
| Apache Software Foundation/Apache Camel JMSgeneric | >=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 |
Published upstream
Apr 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.
CVSS is 9.9. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps Apache Software Foundation/Apache Camel CoAP (generic), Apache Software Foundation/Apache Camel Google PubSub (generic), Apache Software Foundation/Apache Camel JMS (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| Apache Software Foundation/Apache Camel CoAPgeneric | >=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 |
| Apache Software Foundation/Apache Camel Google PubSubgeneric | >=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 |
| Apache Software Foundation/Apache Camel JMSgeneric | >=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 |
Published upstream
Apr 27, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Jul 15, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Jul 15, 2026
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.
Quoted source text, attributed separately from HOL analysis.