Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CWE-441 (未有动机的代理或中间人(混淆代理)) — Vulnerability Class 96

96 vulnerabilities classified as CWE-441 (未有动机的代理或中间人(混淆代理)). AI Chinese analysis included.

CWE-441 represents a design flaw where a system acts as an unintended intermediary, failing to preserve the original requestor’s identity when forwarding messages to external actors. This weakness allows attackers to exploit the system by manipulating upstream components to issue malicious requests that appear to originate from the trusted application itself. Consequently, the vulnerable software performs actions on behalf of the attacker, potentially bypassing access controls or triggering unintended side effects within protected resources. To mitigate this risk, developers must implement robust identity preservation mechanisms, such as cryptographic signing or secure token passing, ensuring that the true source of every request is explicitly validated and maintained throughout the communication chain. By strictly enforcing source authentication and avoiding blind forwarding, organizations can prevent their systems from being coerced into acting as confused deputies for unauthorized operations.

MITRE CWE Description
The product receives a request, message, or directive from an upstream component, but the product does not sufficiently preserve the original source of the request before forwarding the request to an external actor that is outside of the product's control sphere. This causes the product to appear to be the source of the request, leading it to act as a proxy or other intermediary between the upstream component and the external actor. If an attacker cannot directly contact a target, but the product has access to the target, then the attacker can send a request to the product and have it be forwarded to the target. The request would appear to be coming from the product's system, not the attacker's system. As a result, the attacker can bypass access controls (such as firewalls) or hide the source of malicious requests, since the requests would not be coming directly from the attacker. Since proxy functionality and message-forwarding often serve a legitimate purpose, this issue only becomes a vulnerability when: The product runs with different privileges or on a different system, or otherwise has different levels of access than the upstream component; The attacker is prevented from making the request directly to the target; and The attacker can create a request that the proxy does not explicitly intend to be forwarded on the behalf of the requester. Such a request might point to an unexpected hostname, port number, hardware IP, or service. Or, the request might be sent to an allo…
Common Consequences (1)
Non-Repudiation, Access Control Gain Privileges or Assume Identity, Hide Activities, Execute Unauthorized Code or Commands
Mitigations (2)
Architecture and Design Enforce the use of strong mutual authentication mechanism between the two parties.
Architecture and Design Whenever a product is an intermediary or proxy for transactions between two other components, the proxy core should not drop the identity of the initiator of the transaction. The immutability of the identity of the initiator must be maintained and should be forwarded all the way to the target.
Examples (1)
A SoC contains a microcontroller (running ring-3 (least trusted ring) code), a Memory Mapped Input Output (MMIO) mapped IP core (containing design-house secrets), and a Direct Memory Access (DMA) controller, among several other compute elements and peripherals. The SoC implements access control…
The code in ring-3 (least trusted ring) of the
                     microcontroller attempts to directly read the protected
                     registers in IP core through MMIO transactions. However,
                     this attempt is blocked due to the implemented access
                     control. Now, the microcontroller configures the DMA core
                     to transfer data from the protected registers to a memory
                     region that it has access to. The DMA core, which is
                     acting as an intermediary in this transaction, does not
              
Bad · Other
The DMA
                     core forwards this transaction with the identity of the
                     code executing on the microcontroller, which is the
                     original initiator of the end-to-end transaction. Now the
                     transaction is blocked, as a result of forwarding the
                     identity of the true initiator which lacks the permission
                     to access the confidential MMIO mapped IP core.
Good · Other
CVE ID Title CVSS Severity Published
CVE-2026-118687 Coder before 2.29.21, 2.34.12, 2.35.9, 2.36.7, and 2.37.4 Missing Audience Validation in GCP Instance-Identity Authentication — coder 6.5 Medium 2026-10-28
CVE-2026-114478 Unintended Proxy or Intermediary ('Confused Deputy') in hMailServer — hMailServer 5.9 Medium 2026-10-21
CVE-2026-105311 Console-operator: streams for apache kafka console: cross-namespace kafkauser secret exfiltration via confused deputy — StreamsHub Console for Apache Kafka® 7.7 High 2026-10-20
CVE-2026-70148 Windows Broadcast DVR User Service Information Disclosure Vulnerability — Windows 10 Version 1809 6.5 Medium 2026-10-13
CVE-2026-83837 Windows Kernel-Mode Drivers Elevation of Privilege Vulnerability — Windows 10 Version 1607 7.8 High 2026-10-13
CVE-2026-93294 Azure Monitor data source resource proxy allows calls to arbitrary Azure Resource Manager APIs — Grafana Enterprise 6.3 Medium 2026-10-13
CVE-2026-109373 ZITADEL 3.0.0 before 4.19.2 Account Takeover via Unsigned Login V2 Session Cookie — zitadel 8.1 High 2026-10-12
CVE-2026-106487 Backstage: Unsupported catalog cluster authentication mode in kubernetes backend — backstage 3.5 Low 2026-10-06
CVE-2026-106462 Backstage: Scaffolder credential handling may allow unintended GitHub authentication fallback — backstage 6.4 Medium 2026-10-06
CVE-2026-94205 Gitea fork workflow approval bypass through maintainer-triggered events — Gitea - - 2026-10-06
CVE-2026-106221 Android Chrome低版本WebAPK混淆副手漏洞 — Chrome - - 2026-10-06
CVE-2026-106427 Chrome iOS<155.0.8059.39混淆副手漏洞 — Chrome - - 2026-10-06
CVE-2026-106359 Chrome<155.0.8059.39混淆副手漏洞可绕过网页起源策略 — Chrome - - 2026-10-06
CVE-2026-106301 Chrome <155.0.8059.39混淆副手漏洞 — Chrome - - 2026-10-06
CVE-2026-106228 Chrome < 155.0.8059.39 Lens混淆副手漏洞 — Chrome - - 2026-10-06
CVE-2026-106188 Chrome Android <155.0.8059.39 登录混淆代理漏洞 — Chrome - - 2026-10-06
CVE-2026-106326 Chrome Android<155.0.8059.39混淆副手漏洞 — Chrome - - 2026-10-06
CVE-2026-106266 Chrome<155.0.8059.39混淆副手漏洞 — Chrome - - 2026-10-06
CVE-2026-106286 Chrome<155.0.8059.39混淆副手漏洞 — Chrome - - 2026-10-06
CVE-2026-93320 BuildKit improperly handles special files in build snapshots — BuildKit 6.0 Medium 2026-10-05
CVE-2026-95328 Android版Chrome 154前混淆代理致信息泄露 — Chrome - - 2026-09-29
CVE-2026-95361 Chrome 154.0.8037.57 前DevTools源策略绕过 — Chrome - - 2026-09-29
CVE-2026-101907 Axios: maxRedirects: 0 is not enforced by the fetch adapter, allowing redirect-based SSRF — axios 7.0 High 2026-09-28
CVE-2026-101905 Axios: Node HTTP adapter prototype-pollution gadget allows request socket hijack via inherited createConnection — axios 7.6 High 2026-09-28
CVE-2026-72668 Unintended Proxy or Intermediary ('Confused Deputy') in Kibana Leading to Privilege Escalation — Kibana 7.3 High 2026-09-26
CVE-2026-100706 kyverno before 1.19.1 Privilege Escalation via Policy apiCall urlPath — kyverno 9.9 Critical 2026-09-26
CVE-2026-100625 Capgo Build Upload Proxy Authorization Bypass via TUS Resource — capgo.app 7.1 High 2026-09-26
CVE-2026-75886 Openshift/console: openshift/console: unauthenticated reverse proxy to in-cluster catalogd service with session token forwarding — Red Hat OpenShift Container Platform 4.17 7.2 High 2026-09-23
CVE-2026-69399 Azure Arc Elevation of Privilege Vulnerability — Azure ARC 10.0 Critical 2026-09-17
CVE-2026-50022 Metacat acts as unintended proxy to backend Apache SOLR engine — metacat 5.8 Medium 2026-09-17

Vulnerabilities classified as CWE-441 (未有动机的代理或中间人(混淆代理)) represent 96 CVEs. The CWE taxonomy describes the weakness; review individual CVEs for product-specific impact.