# CVE-2026-46592: 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 > Attackers can redirect SOAP operations by injecting unfiltered HTTP headers, potentially executing destructive actions on backend services. - **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 6 Jul 2026 - **Updated:** 6 Jul 2026 - **Also known as:** GHSA-mrrp-9gjm-749v ## What is CVE-2026-46592? CVE-2026-46592 is a high-severity vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official 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. Weakness: CWE-441 (Unintended Proxy or Intermediary), CWE-20 (Improper Input Validation) ## Which versions are affected by CVE-2026-46592? 12 open source packages ship an affected version, including org.apache.camel:camel-cxf-rest and org.apache.camel:camel-cxf-soap. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `org.apache.camel:camel-cxf-rest` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-cxf-rest` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-cxf-rest` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-cxf-rest` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-cxf-rest` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-cxf-rest` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-cxf-soap` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-cxf-soap` | Maven | From 4.0.0 | 4.14.8 | | `org.apache.camel:camel-cxf-soap` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-cxf-soap` | Maven | From 4.15.0 | 4.18.3 | | `org.apache.camel:camel-cxf-soap` | Maven | From 4.19.0 | 4.21.0 | | `org.apache.camel:camel-cxf-soap` | Maven | From 4.19.0 | 4.21.0 | Products: Apache Camel. ## How do I fix CVE-2026-46592? Upgrade org.apache.camel:camel-cxf-rest to a fixed version for your release line: 4.14.8, 4.18.3 or 4.21.0. ## Is CVE-2026-46592 being exploited? There is no known exploitation of CVE-2026-46592 in the wild and no public exploit code. Public exploit code: - Reproducer for CVE-2026-46592: Apache Camel camel-cxf operationName header injection redirecting the invoked SOAP operation (confused deputy) from a read to a destructive one (fixed in 4.14.8/4.18.3/4.21.0) (github_poc): https://github.com/oscerd/CVE-2026-46592 ## 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-40453](https://insights.sbomify.com/CVE-2026-40453/): Apache Camel has an incomplete fix for CVE-2025-27636 (critical 9.9) - [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) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-46592 and fix it if it is affected. What it is: CVE-2026-46592 is a high-severity vulnerability in Apache Camel, published on 6 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-46592 in the wild and no public exploit code. Affected packages and fixed versions: - org.apache.camel:camel-cxf-rest (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-cxf-rest (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-cxf-rest (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-cxf-rest (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-cxf-rest (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-cxf-rest (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-cxf-soap (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-cxf-soap (Maven): affected from 4.0.0; fixed in 4.14.8 - org.apache.camel:camel-cxf-soap (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-cxf-soap (Maven): affected from 4.15.0; fixed in 4.18.3 - org.apache.camel:camel-cxf-soap (Maven): affected from 4.19.0; fixed in 4.21.0 - org.apache.camel:camel-cxf-soap (Maven): affected from 4.19.0; fixed in 4.21.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-46592/ (Markdown: https://insights.sbomify.com/CVE-2026-46592/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-46592 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-46592 - OSV: https://osv.dev/vulnerability/CVE-2026-46592 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-46592/ Summaries are generated and may contain mistakes; the official description above is the record.