# Apache Camel-CXF: The SOAP operation-selection headers used non-Camel-prefixed names (operationName, operationNamespace) that bypass the HTTP header filter, allowing an HTTP client to redirect the invoked SOAP operation Advisory record · `GHSA-mrrp-9gjm-749v` - **Identifiers:** `GHSA-mrrp-9gjm-749v` · `CVE-2026-46592` - **State:** Confirmed - **Severity:** CVSS 7.5 High - **Critical:** No - **Weakness (CWE):** [CWE-20](https://cwe.mitre.org/data/definitions/20.html) · [CWE-441](https://cwe.mitre.org/data/definitions/441.html) - **Tags:** [CWE-20](https://agentprime.io/advisories/tag/cwe-20.md) · [CWE-441](https://agentprime.io/advisories/tag/cwe-441.md) - **Published:** 6 Jul 2026 - **Updated:** 28 Aug 2026 - **Reviewed by a person:** No Published by the GitHub Advisory Database at 6 Jul 2026, 09:30 UTC. agentprime has not analysed this yet, so whether it affects any app is not known. ## Affected packages - `org.apache.camel:camel-cxf-soap` (Maven): affected `>=4.0.0, <4.14.8 || >=4.15.0, <4.18.3 || >=4.19.0, <4.21.0`; fixed in `4.14.8`, `4.18.3`, `4.21.0` - `org.apache.camel:camel-cxf-rest` (Maven): affected `>=4.0.0, <4.14.8 || >=4.15.0, <4.18.3 || >=4.19.0, <4.21.0`; fixed in `4.14.8`, `4.18.3`, `4.21.0` ## Machine-written summary Summary written by Claude Haiku from the source advisory. Not reviewed by a person. > Apache Camel's camel-cxf-soap and camel-cxf-rest packages, versions from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, and from 4.19.0 before 4.21.0, let an unauthenticated HTTP client set the operationName and operationNamespace headers when a route bridges an HTTP consumer into a cxf producer. This can redirect the SOAP operation invoked on the backend service, for example to a destructive one. Upgrade to 4.14.8, 4.18.3, or 4.21.0 depending on your release stream. Until then, strip those two headers from untrusted input before the cxf producer and set the operation from a trusted source. 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 - 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`, from GitHub Advisory Database - **CISA KEV:** Not listed. - **EPSS:** 0.0063, the 50th percentile, on 6 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days. ## Timeline - 31 Oct 2026, 14:19 UTC: First seen by agentprime - 31 Oct 2026, 14:19 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-mrrp-9gjm-749v) ## Sources - [GitHub Advisory Database: GHSA-mrrp-9gjm-749v](https://github.com/advisories/GHSA-mrrp-9gjm-749v) - [OSV: GHSA-mrrp-9gjm-749v](https://osv.dev/vulnerability/GHSA-mrrp-9gjm-749v) - - - - - - - - - - - - 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: .