Loading...
Skip to main content

CVE-2026-46592 — Vulnerability in org.apache.camel:camel-cxf-rest...

HIGH

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

Published July 6, 2026Updated August 28, 2026Source: osv

Summary

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.

Advisory Timeline

  • First published July 6, 2026 (98 days ago).
  • Last revised August 28, 2026 — 53 days after initial publication.

Remediation

Upgrade to the fixed version using your package manager.

Maven
Update org.apache.camel:camel-cxf-rest to 4.18.3 or later
<!-- Update pom.xml dependency version to 4.18.3 for org.apache.camel:camel-cxf-rest -->
Maven
Update org.apache.camel:camel-cxf-soap to 4.21.0 or later
<!-- Update pom.xml dependency version to 4.21.0 for org.apache.camel:camel-cxf-soap -->
Maven
Update org.apache.camel:camel-cxf-rest to 4.21.0 or later
<!-- Update pom.xml dependency version to 4.21.0 for org.apache.camel:camel-cxf-rest -->
Maven
Update org.apache.camel:camel-cxf-soap to 4.18.3 or later
<!-- Update pom.xml dependency version to 4.18.3 for org.apache.camel:camel-cxf-soap -->
Maven
Update org.apache.camel:camel-cxf-rest to 4.14.8 or later
<!-- Update pom.xml dependency version to 4.14.8 for org.apache.camel:camel-cxf-rest -->
Maven
Update org.apache.camel:camel-cxf-soap to 4.14.8 or later
<!-- Update pom.xml dependency version to 4.14.8 for org.apache.camel:camel-cxf-soap -->

After upgrading, run your dependency scanner again to confirm the vulnerability is resolved.

Affected Packages (6)

Affects 1 ecosystem: maven (2).

PackageEcosystemAffectedFixed In
org.apache.camel:camel-cxf-rest
maven
4.15.0, 4.16.0, 4.17.0, 4.18.0 (+2 more)4.18.3
org.apache.camel:camel-cxf-soap
maven
4.19.0, 4.20.04.21.0
org.apache.camel:camel-cxf-rest
maven
4.19.0, 4.20.04.21.0
org.apache.camel:camel-cxf-soap
maven
4.15.0, 4.16.0, 4.17.0, 4.18.0 (+2 more)4.18.3
org.apache.camel:camel-cxf-rest
maven
4.0.0, 4.0.1, 4.0.2, 4.0.3 (+47 more)4.14.8
org.apache.camel:camel-cxf-soap
maven
4.0.0, 4.0.1, 4.0.2, 4.0.3 (+47 more)4.14.8

Vulnerability Classification

Common Weakness Enumeration (CWE) identifiers for this vulnerability type.

CVSS Score Breakdown

What the CVSS (Common Vulnerability Scoring System) 7.5 score means for each attack dimension.

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Frequently Asked Questions

What is 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 This vulnerability has been assigned a severity rating of HIGH (CVSS score: 7.5/10).
How do I check if my project is affected by CVE-2026-46592?
CVE-2026-46592 affects org.apache.camel:camel-cxf-rest and org.apache.camel:camel-cxf-soap. Use GeekWala's free vulnerability scanner to check your dependencies against CVE-2026-46592 and 200,000+ other known vulnerabilities.

Severity & Exploitability

CVSS Score
7.5

High exploitability or significant impact. Prioritize remediation within days.

Also Known As

GHSA-mrrp-9gjm-749v

Related CVEs

  • CVE-2026-47323
    CRITICAL

    Camel-CXF and Camel-Knative Message Header are Vulnerable to Injection via Missing Inbound Filtering

  • CVE-2026-40453
    CRITICAL

    Apache Camel has an incomplete fix for CVE-2025-27636

  • CVE-2026-40860
    CRITICAL

    Apache camel-jms, camel-sjms, camel-sjms2 and camel-amqp: Unsafe Deserialization of JMS ObjectMessage

  • CVE-2026-46455
    CRITICAL

    Apache Camel-Keycloak: The access-token validity window is not verified because the IS_ACTIVE check is missing from the TokenVerifier, allowing expired tokens to be accepted

  • CVE-2026-40859
    HIGH

    Apache Camel-Vertx-Http and Camel-Netty-Http: Unsafe Java deserialization of HTTP response bodies via a raw ObjectInputStream when transferException is enabled

  • CVE-2026-42527
    HIGH

    Apache Camel: Permissive default ObjectInputFilter pattern admits java.net.** and enables DNS-based information disclosure

  • CVE-2026-43866
    HIGH

    Apache Camel JMS deserialization filter bypass

  • CVE-2026-46591
    HIGH

    Apache Camel-Neo4j: JSON property names from the CamelNeo4jMatchProperties header are interpolated into the Cypher WHERE clause without validation, allowing Cypher injection (incomplete remediation of CVE-2025-66169)

Check if you're affected

Scan your dependencies to see if this vulnerability affects your projects.

Scan Your Dependencies