CVE-2026-40453

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.

CVE-2026-40453 has a CVSS score of 9.9 (Critical). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (4.14.6, 4.18.2, 4.20.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-40453? CVE-2026-40453 is a critical-severity security vulnerability in org.apache.camel:camel-coap (maven), affecting versions >= 3.0.0, < 4.14.6. It is fixed in 4.14.6, 4.18.2, 4.20.0.
2. How severe is CVE-2026-40453? CVE-2026-40453 has a CVSS score of 9.9 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2026-40453?
   • org.apache.camel:camel-coap (maven) (versions >= 3.0.0, < 4.14.6)
   • org.apache.camel:camel-google-pubsub (maven) (versions >= 3.0.0, < 4.14.6)
   • org.apache.camel:camel-jms (maven) (versions >= 3.0.0, < 4.14.6)
   • org.apache.camel:camel-sjms (maven) (versions >= 3.0.0, < 4.14.6)
4. Is there a fix for CVE-2026-40453? Yes. CVE-2026-40453 is fixed in 4.14.6, 4.18.2, 4.20.0. Upgrade to this version or later.
5. Is CVE-2026-40453 exploitable, and should I be worried? Whether CVE-2026-40453 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-40453 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-40453?
   • Upgrade org.apache.camel:camel-coap to 4.14.6 or later
   • Upgrade org.apache.camel:camel-coap to 4.18.2 or later
   • Upgrade org.apache.camel:camel-coap to 4.20.0 or later
   • Upgrade org.apache.camel:camel-google-pubsub to 4.14.6 or later
   • Upgrade org.apache.camel:camel-google-pubsub to 4.18.2 or later
   • Upgrade org.apache.camel:camel-google-pubsub to 4.20.0 or later
   • Upgrade org.apache.camel:camel-jms to 4.14.6 or later
   • Upgrade org.apache.camel:camel-jms to 4.18.2 or later
   • Upgrade org.apache.camel:camel-jms to 4.20.0 or later
   • Upgrade org.apache.camel:camel-sjms to 4.14.6 or later
   • Upgrade org.apache.camel:camel-sjms to 4.18.2 or later
   • Upgrade org.apache.camel:camel-sjms to 4.20.0 or later