CVE-2026-46592: CWE-20 Improper Input Validation in Apache Software Foundation Apache Camel
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.
AI Analysis
Technical Summary
The vulnerability arises because the camel-cxf producer uses the operationName and operationNamespace Exchange headers, which are not prefixed with 'Camel' and thus bypass the HttpHeaderFilterStrategy that filters headers at HTTP boundaries. This allows an attacker sending HTTP requests to set these headers and cause the cxf: producer to invoke a different SOAP operation than intended by the route, leading to a confused-deputy scenario. No authentication is required if the bridging consumer is unauthenticated. The issue affects Apache Camel 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. The vulnerability is fixed in versions 4.14.8, 4.18.3, and 4.21.0, where the operation-selection headers are renamed with a Camel prefix and filtered at transport boundaries.
Potential Impact
An attacker can cause the backend SOAP service to execute unintended operations by manipulating HTTP headers, potentially replacing safe read operations with destructive ones. This can lead to unauthorized actions on the backend service without requiring credentials if the HTTP consumer is unauthenticated.
Mitigation Recommendations
A fix is available in Apache Camel versions 4.14.8, 4.18.3, and 4.21.0. Users are strongly recommended to upgrade to these versions. For users unable to upgrade immediately, it is advised to strip the operationName and operationNamespace headers from any untrusted ingress before the cxf: producer and set the operation from a trusted source within the route. After upgrading, the operation-selection headers are renamed to CamelCxfOperationName and CamelCxfOperationNamespace and are filtered at transport boundaries.
CVE-2026-46592: CWE-20 Improper Input Validation in Apache Software Foundation Apache Camel
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.
CVSS v3.1
Score 7.5high
Affected software
pkg:maven/Apache Software Foundation/org.apache.camel:camel-cxf-soapRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability arises because the camel-cxf producer uses the operationName and operationNamespace Exchange headers, which are not prefixed with 'Camel' and thus bypass the HttpHeaderFilterStrategy that filters headers at HTTP boundaries. This allows an attacker sending HTTP requests to set these headers and cause the cxf: producer to invoke a different SOAP operation than intended by the route, leading to a confused-deputy scenario. No authentication is required if the bridging consumer is unauthenticated. The issue affects Apache Camel 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. The vulnerability is fixed in versions 4.14.8, 4.18.3, and 4.21.0, where the operation-selection headers are renamed with a Camel prefix and filtered at transport boundaries.
Potential Impact
An attacker can cause the backend SOAP service to execute unintended operations by manipulating HTTP headers, potentially replacing safe read operations with destructive ones. This can lead to unauthorized actions on the backend service without requiring credentials if the HTTP consumer is unauthenticated.
Mitigation Recommendations
A fix is available in Apache Camel versions 4.14.8, 4.18.3, and 4.21.0. Users are strongly recommended to upgrade to these versions. For users unable to upgrade immediately, it is advised to strip the operationName and operationNamespace headers from any untrusted ingress before the cxf: producer and set the operation from a trusted source within the route. After upgrading, the operation-selection headers are renamed to CamelCxfOperationName and CamelCxfOperationNamespace and are filtered at transport boundaries.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- apache
- Date Reserved
- 2026-05-15T13:32:13.841Z
- Cvss Version
- null
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a4b6cae27e9c7971925236d
Added to database: 07/06/2026, 08:51:58 UTC
Last enriched: 07/06/2026, 09:08:31 UTC
Last updated: 07/06/2026, 23:07:49 UTC
Views: 4
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.