# Apache Camel has an incomplete fix for CVE-2025-27636 Advisory record · `GHSA-jg2m-9x48-3gvj` - **Identifiers:** `GHSA-jg2m-9x48-3gvj` · `CVE-2026-40453` - **State:** Confirmed - **Severity:** CVSS 9.9 Critical - **Critical:** Yes: CVSS 9+ - **Weakness (CWE):** [CWE-178](https://cwe.mitre.org/data/definitions/178.html) - **Tags:** [CWE-178](https://agentprime.io/advisories/tag/cwe-178.md) - **Published:** 27 Apr 2026 - **Updated:** 5 Oct 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 27 Apr 2026, 09:34 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Critical Critical, because: - CVSS score 9.9: 9.0 or more. How we decide what’s critical: ## Affected packages - `org.apache.camel:camel-coap` (Maven): affected `>=3.0.0, <4.14.6 || >=4.15.0, <4.18.2 || >=4.19.0, <4.20.0`; fixed in `4.14.6`, `4.18.2`, `4.20.0` - `org.apache.camel:camel-google-pubsub` (Maven): affected `>=3.0.0, <4.14.6 || >=4.15.0, <4.18.2 || >=4.19.0, <4.20.0`; fixed in `4.14.6`, `4.18.2`, `4.20.0` - `org.apache.camel:camel-jms` (Maven): affected `>=3.0.0, <4.14.6 || >=4.15.0, <4.18.2 || >=4.19.0, <4.20.0`; fixed in `4.14.6`, `4.18.2`, `4.20.0` - `org.apache.camel:camel-sjms` (Maven): affected `>=3.0.0, <4.14.6 || >=4.15.0, <4.18.2 || >=4.19.0, <4.20.0`; fixed in `4.14.6`, `4.18.2`, `4.20.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Camel's camel-coap, camel-google-pubsub, camel-jms and camel-sjms modules are affected from 3.0.0 before 4.14.6, from 4.15.0 before 4.18.2, and from 4.19.0 before 4.20.0. An attacker with producer access to a JMS or equivalent broker consumed by a Camel route can inject case-variant internal headers, which can lead to remote code execution or arbitrary file write in routes that forward messages to header-driven components. Upgrade to 4.14.6, 4.18.2, or 4.20.0 depending on your release stream. Written 2 Nov 2026. ## Not analysed yet We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check. ## Severity and exploitation - 9.9 Critical, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.021, the 81st percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:16 UTC: First seen by agentprime - 31 Oct 2026, 14:16 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-jg2m-9x48-3gvj) ## Sources - [GitHub Advisory Database: GHSA-jg2m-9x48-3gvj](https://github.com/advisories/GHSA-jg2m-9x48-3gvj) - [OSV: GHSA-jg2m-9x48-3gvj](https://osv.dev/vulnerability/GHSA-jg2m-9x48-3gvj) - - - - - - - - - - - - Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code. ## Check whether this affects you A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet. - With the agentprime MCP server (), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: - In a browser: reads your lockfile in the browser, never uploading it. - Whether it touches your code, with file and line: the Claude Code plugin, - As JSON: , or `POST https://api.agentprime.io/v1/match` with your packages () --- The web page: . Everything for agents: .