CVE-2026-46592 is a high-severity (CVSS 7.5) Improper Input Validation vulnerability in org.apache.camel:camel-cxf-soap. A fix is available for org.apache.camel:camel-cxf-soap — see the affected versions and patch details below.
Apache Camel: 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
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2026-46592.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2026-46592 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
org.apache.camel:camel-cxf-soap☕org.apache.camel:camel-cxf-soap☕org.apache.camel:camel-cxf-soap☕org.apache.camel:camel-cxf-rest☕org.apache.camel:camel-cxf-rest☕org.apache.camel:camel-cxf-restReal-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
Improper Input Validation, Unintended Proxy or Intermediary ('Confused Deputy') vulnerability in Apache Camel CXF SOAP component.
The camel-cxf producer selects which SOAP operation to invoke on the backend service from the operationName (and operationNamespace) Exchange header, whose constant values (CxfConstants.OPERATION_NAME / OPERATION_NAMESPACE) were the plain strings operationName / operationNamespace. Because these names do not start with the Camel / camel prefix, HttpHeaderFilterStrategy - which blocks only the Camel header namespace on the HTTP boundary - let them pass from an inbound HTTP request straight into the Exchange. In a route that bridges an HTTP consumer (for example platform-http) into a cxf: producer, any HTTP client could therefore set the operationName header and have CxfProducer resolve and invoke a different WSDL operation than the route intended - for example replacing a read operation with a destructive one - against the backend SOAP service (a confused-deputy redirection). The constant is defined in the shared camel-cxf-common module, so the same non-prefixed names also applied to camel-cxfrs. No credentials are required when the bridging consumer is unauthenticated. This issue affects Apache Camel: from 4.0.0 before 4.14.8, from 4.15.0 before 4.18.3, from 4.19.0 before 4.21.0.
Users are recommended to upgrade to version 4.21.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.8. If users are on the 4.18.x releases stream, then they are suggested to upgrade to 4.18.3. After upgrading, the operation-selection headers are named CamelCxfOperationName / CamelCxfOperationNamespace and are filtered at transport boundaries; see the 4.21 upgrade guide for the cross-transport carrier-header pattern. For deployments that cannot upgrade immediately, do not select the CXF operation from untrusted input: strip the operationName and operationNamespace headers from any untrusted ingress before the cxf: producer and set the operation from a trusted source in the route.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| ☕Maven | org.apache.camel:camel-cxf-soap | ≥ 4.0.0&&< 4.14.8 | 4.14.8org.apache.camel:camel-cxf-soap:4.14.8 |
| ☕Maven | org.apache.camel:camel-cxf-soap | ≥ 4.15.0&&< 4.18.3 | 4.18.3org.apache.camel:camel-cxf-soap:4.18.3 |
| ☕Maven | org.apache.camel:camel-cxf-soap | ≥ 4.19.0&&< 4.21.0 | 4.21.0org.apache.camel:camel-cxf-soap:4.21.0 |
| ☕Maven | org.apache.camel:camel-cxf-rest | ≥ 4.0.0&&< 4.14.8 | 4.14.8org.apache.camel:camel-cxf-rest:4.14.8 |
| ☕Maven | org.apache.camel:camel-cxf-rest | ≥ 4.15.0&&< 4.18.3 | 4.18.3org.apache.camel:camel-cxf-rest:4.18.3 |
| ☕Maven | org.apache.camel:camel-cxf-rest | ≥ 4.19.0&&< 4.21.0 | 4.21.0org.apache.camel:camel-cxf-rest:4.21.0 |
Affected Products
camelapacheDetection & 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-cxf-soap, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.apache.camel:camel-cxf-soap to 4.14.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2026-46592 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.
Fixing This On Your OS
If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.
This is an Important flaw in the Apache Camel CXF SOAP component, allowing a remote, unauthenticated attacker to manipulate SOAP operation names via HTTP headers. When an HTTP consumer bridges into a `cxf:` producer, an attacker can force the backend service to execute unintended operations, potentially replacing read…
To mitigate this issue, ensure that the `operationName` and `operationNamespace` headers are not sourced from untrusted input when bridging an HTTP consumer to a `cxf:` producer in Apache Camel routes. Configure the route to explicitly strip these headers from any untrusted ingress before they reach the `cxf:` producer. Subsequently, set the intended SOAP operation from a trusted, internal source within the route. This prevents a remote attacker from manipulating backend service operations. Changes to route configurations may require a service restart to take effect.Source: Red Hat security advisory for CVE-2026-46592 (CC BY 4.0)
| Product | Fixed in | Advisory |
|---|---|---|
| Red Hat Build of Apache Camel 3.33.2.SP3 | org.apache.camel/camel-cxf-common:4.18.3.redhat-00001 | RHSA-2026:48118 |
| Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16 | camel-cxf-common | RHSA-2026:54622 |
Frequently Asked Questions
Is CVE-2026-46592 in your dependencies?
Find it across Maven, including transitive dependencies.