cve.bz

CVE-2026-46592 apache camel: Confused Deputy

7.5 highEPSS 0.6%Fix available

High (7.5) in apache camel. EPSS 0.6% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.camel:camel-cxf-soap 4.14.8, 4.18.3, 4.21.0.

On this page
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.

Severity

CVSS 3.1

7.5 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
EPSS
0.6% (unchanged from 0.6% a week ago; 0.6% 30 days ago) estimated probability of exploitation activity in the next 30 days; 51st percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: yes · Technical impact: partial, assessed 2026-07-06. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-20 Improper Input Validation
CWE-441 Unintended Proxy or Intermediary (Confused Deputy)
OWASP Top 10
A01:2025 Broken Access Control, A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-46592 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-46592?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-46592?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-46592 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-46592

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-46592](https://cve.bz/cve/badge/CVE-2026-46592.svg)](https://cve.bz/cve/CVE-2026-46592)

HTML:

<a href="https://cve.bz/cve/CVE-2026-46592"><img src="https://cve.bz/cve/badge/CVE-2026-46592.svg" alt="CVE-2026-46592"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Apache Software Foundation Apache Camelfrom 4.0.0 before 4.14.8
Apache Software Foundation Apache Camelfrom 4.15.0 before 4.18.3
Apache Software Foundation Apache Camelfrom 4.19.0 before 4.21.0

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mrrp-9gjm-749vMavenorg.apache.camel:camel-cxf-soap>=4.0.0 <4.14.84.14.8
GHSA-mrrp-9gjm-749vMavenorg.apache.camel:camel-cxf-soap>=4.15.0 <4.18.34.18.3
GHSA-mrrp-9gjm-749vMavenorg.apache.camel:camel-cxf-soap>=4.19.0 <4.21.04.21.0
GHSA-mrrp-9gjm-749vMavenorg.apache.camel:camel-cxf-rest>=4.0.0 <4.14.84.14.8
GHSA-mrrp-9gjm-749vMavenorg.apache.camel:camel-cxf-rest>=4.15.0 <4.18.34.18.3
GHSA-mrrp-9gjm-749vMavenorg.apache.camel:camel-cxf-rest>=4.19.0 <4.21.04.21.0

Red Hat

Red Hat rates this Important.

Red Hat's statement

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 operations with destructive ones. This 'confused deputy' scenario impacts the integrity of services utilizing affected Red Hat build of Apache Camel and Enterprise Application Platform configurations.

Red Hat's mitigation

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.

ProductPackageStateAdvisory
Red Hat Build of Apache Camel 3.33.2.SP3org.apache.camel/camel-cxf-common:4.18.3.redhat-00001Fixed 2026-07-30RHSA-2026:48118
Red Hat build of Apache Camel 4.18.3 for Spring Boot 3.5.16camel-cxf-commonFixed 2026-08-13RHSA-2026:54622
Red Hat build of Apache Camel 4 for Quarkus 3camel-cxf-commonAffected
Red Hat JBoss Enterprise Application Platform Expansion Packcamel-cxf-commonNot affected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-46592.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

  • oscerd/CVE-2026-46592 Harbor Check: matches CVE 0 stars, Java, created
    Reproducer for CVE-2026-46592: Apache Camel camel-cxf operationName header injection redirecting the invoked SOAP operation (confused deput…

Attack patterns (CAPEC)

  • CAPEC-219 XML Routing Detour Attacks Likelihood: High · Severity: Medium
  • CAPEC-465 Transparent Proxy Abuse Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-20 (51).

References

Check your stackJSON