# CVE-2026-40453: Apache Camel has an incomplete fix for CVE-2025-27636 > Attackers can inject case-variant headers in JMS, CoAP, or PubSub routes to trigger remote code execution or arbitrary file writes via downstream components. - **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 27 Apr 2026 - **Updated:** 15 Jul 2026 - **Also known as:** CLEANSTART-2026-AM66642, GHSA-jg2m-9x48-3gvj, MINI-2mch-7h58-4h6v, MINI-34v2-xcg4-fxm4, MINI-66j5-8vm7-c8vr, MINI-7g54-92q4-j2f5 ## What is CVE-2026-40453? CVE-2026-40453 is a critical code injection vulnerability in Apache Camel, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official 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. Weakness: CWE-178 (Improper Handling of Case Sensitivity) ## Which versions are affected by CVE-2026-40453? 24 open source packages ship an affected version, including org.apache.camel:camel-coap, org.apache.camel:camel-google-pubsub and org.apache.camel:camel-jms. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-coap` | Maven | From 3.0.0 | 4.14.6 | | `org.apache.camel:camel-coap` | Maven | From 3.0.0 | 4.14.6 | | `org.apache.camel:camel-coap` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-coap` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-coap` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-coap` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-google-pubsub` | Maven | From 3.0.0 | 4.14.6 | | `org.apache.camel:camel-google-pubsub` | Maven | From 3.0.0 | 4.14.6 | | `org.apache.camel:camel-google-pubsub` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-google-pubsub` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-google-pubsub` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-google-pubsub` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-jms` | Maven | From 3.0.0 | 4.14.6 | | `org.apache.camel:camel-jms` | Maven | From 3.0.0 | 4.14.6 | | `org.apache.camel:camel-jms` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-jms` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-jms` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-jms` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-sjms` | Maven | From 3.0.0 | 4.14.6 | | `org.apache.camel:camel-sjms` | Maven | From 3.0.0 | 4.14.6 | | `org.apache.camel:camel-sjms` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-sjms` | Maven | From 4.15.0 | 4.18.2 | | `org.apache.camel:camel-sjms` | Maven | From 4.19.0 | 4.20.0 | | `org.apache.camel:camel-sjms` | Maven | From 4.19.0 | 4.20.0 | Products: Apache Camel. ## How do I fix CVE-2026-40453? Upgrade org.apache.camel:camel-coap to a fixed version for your release line: 4.14.6, 4.18.2 or 4.20.0. ## Is CVE-2026-40453 being exploited? There is no known exploitation of CVE-2026-40453 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-40453: Apache Camel case-variant Camel header injection (incomplete fix of CVE-2025-27636) (github_poc): https://github.com/oscerd/CVE-2026-40453 ## Other vulnerabilities in Apache Camel - [CVE-2026-33453](https://insights.sbomify.com/CVE-2026-33453/): Apache camel-coap allows header injection that can lead to remote code execution (critical 10.0) - [CVE-2026-80351](https://insights.sbomify.com/CVE-2026-80351/): Apache Camel K: Camel K Tenant repositories reach Maven execution inside operator pod (critical 9.8) - [CVE-2026-80352](https://insights.sbomify.com/CVE-2026-80352/): Apache Camel K: Camel K Master trait serviceAccountName YAML injection lets CR author apply arbitrary objects (critical 9.8) - [CVE-2026-71300](https://insights.sbomify.com/CVE-2026-71300/): Apache Camel: Camel-Atmosphere-Websocket: WebSocket dispatch header injection (critical 9.8) - [CVE-2026-78329](https://insights.sbomify.com/CVE-2026-78329/): Apache Camel-Undertow: the endpoint discarded the undertow-specific header filter strategy in favour of the base HTTP one, so the undertow filtering never ran on endpoint-configured routes (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-40453 and fix it if it is affected. What it is: CVE-2026-40453 is a critical code injection vulnerability in Apache Camel, published on 27 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-40453 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-coap (Maven): affected from 3.0.0; fixed in 4.14.6 - org.apache.camel:camel-coap (Maven): affected from 3.0.0; fixed in 4.14.6 - org.apache.camel:camel-coap (Maven): affected from 4.15.0; fixed in 4.18.2 - org.apache.camel:camel-coap (Maven): affected from 4.15.0; fixed in 4.18.2 - org.apache.camel:camel-coap (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-coap (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-google-pubsub (Maven): affected from 3.0.0; fixed in 4.14.6 - org.apache.camel:camel-google-pubsub (Maven): affected from 3.0.0; fixed in 4.14.6 - org.apache.camel:camel-google-pubsub (Maven): affected from 4.15.0; fixed in 4.18.2 - org.apache.camel:camel-google-pubsub (Maven): affected from 4.15.0; fixed in 4.18.2 - org.apache.camel:camel-google-pubsub (Maven): affected from 4.19.0; fixed in 4.20.0 - org.apache.camel:camel-google-pubsub (Maven): affected from 4.19.0; fixed in 4.20.0 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-40453/ (Markdown: https://insights.sbomify.com/CVE-2026-40453/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-40453 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-40453 - OSV: https://osv.dev/vulnerability/CVE-2026-40453 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-40453/ Summaries are generated and may contain mistakes; the official description above is the record.