GHSA-jg2m-9x48-3gvj is a critical-severity (CVSS 9.9) remote code execution vulnerability in org.apache.camel:camel-coap. O3 Security confirms whether GHSA-jg2m-9x48-3gvj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Apache Camel has an incomplete fix for CVE-2025-27636
Real-World Exposure
org.apache.camel:camel-coap☕org.apache.camel:camel-coap☕org.apache.camel:camel-coap☕org.apache.camel:camel-google-pubsub☕org.apache.camel:camel-google-pubsub☕org.apache.camel:camel-google-pubsub☕org.apache.camel:camel-jms☕org.apache.camel:camel-jms+4 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.
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.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.camel:camel-coap | ≥ 3.0.0&&< 4.14.6 | 4.14.6 |
| ☕Maven | org.apache.camel:camel-coap | ≥ 4.15.0&&< 4.18.2 | 4.18.2 |
| ☕Maven | org.apache.camel:camel-coap | ≥ 4.19.0&&< 4.20.0 | 4.20.0 |
| ☕Maven | org.apache.camel:camel-google-pubsub | ≥ 3.0.0&&< 4.14.6 | 4.14.6 |
| ☕Maven | org.apache.camel:camel-google-pubsub | ≥ 4.15.0&&< 4.18.2 | 4.18.2 |
| ☕Maven | org.apache.camel:camel-google-pubsub | ≥ 4.19.0&&< 4.20.0 | 4.20.0 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.apache.camel:camel-coap. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update org.apache.camel:camel-coap to 4.14.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-jg2m-9x48-3gvj is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-jg2m-9x48-3gvj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-jg2m-9x48-3gvj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-jg2m-9x48-3gvj in your dependencies?
O3 detects GHSA-jg2m-9x48-3gvj across Maven dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.