Skip to content
Fencer Vulns
high 7.5

CVE-2026-46592 json

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

published 2026-07-06 4 mo ago modified 2026-10-25 15 d ago also GHSA-mrrp-9gjm-749v , EUVD-2026-41836

cvss
7.5
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
0.6%
EPSS 0.6% chance of exploitation in 30 days, percentile 50%
public exploits
0
none known

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.

Patch / fix

  • maven org.apache.camel:camel-cxf-soap 4.14.8, 4.18.3, 4.21.0
  • maven org.apache.camel:camel-cxf-rest 4.14.8, 4.18.3, 4.21.0
  • Apache Software Foundation Apache Camel 4.14.8, 4.18.3, 4.21.0

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-46592 updated cvss 7.5

org.apache.camel/camel-cxf: Apache Camel CXF SOAP: Remote attacker can execute unintended operations via header manipulation

  • Red Hat build of Apache Camel 4 for Quarkus 3 camel-cxf-common 4.18.1.redhat-00026
    affected: workaround, no fix available
  • Red Hat Build of Apache Camel 3.33.2.SP3 camel-cxf-common 4.18.3.redhat-00001
    fixed: vendor fix RHSA-2026:48118
  • Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16
    fixed: vendor fix RHSA-2026:54622
  • Red Hat Build of Apache Camel 3.33.2.SP3 jimfs 1.1, jna 5.8.0, bcel 6.7.0, bson 5.6.4, gax 2.74.1, icu4j 78.2, +1630 more
    not affected: vulnerable code not present
  • Red Hat JBoss Enterprise Application Platform Expansion Pack camel-cxf-common 4.18.1.redhat-00026
    not affected: component not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
partial
Assessed
4 mo ago

Exploit prediction

0.63% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
CNA 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
GitHub 3.1 7.5 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected packages

ecosystem package affected fixed in
maven org.apache.camel:camel-cxf-soap
>=4.0.0, <4.14.8
>=4.15.0, <4.18.3
>=4.19.0, <4.21.0
4.14.8
4.18.3
4.21.0
maven org.apache.camel:camel-cxf-rest
>=4.0.0, <4.14.8
>=4.15.0, <4.18.3
>=4.19.0, <4.21.0
4.14.8
4.18.3
4.21.0

Affected products

  • Apache Software Foundation Apache Camel

Classification

Weakness
  • CWE-20 Improper Input Validation
  • CWE-441 Unintended Proxy or Intermediary

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.