Threadlinqs IntelligenceStart free

Weakness · ClassCWE-441

CWE-441: Unintended Proxy or Intermediary ('Confused Deputy')

KEV-linkedClass

As of 2026-11-19, CWE-441 (Confused Deputy) underlies 14 CVEs tracked by Threadlinqs, 1 of them in the CISA Known Exploited Vulnerabilities catalog, and is cited by 21 tracked threats.

CVEs
14Mapped to CWE-441
CISA KEV
1Exploited in the wild
Critical
6CVSS v3 critical CVEs
Threats
21Tracked campaigns citing it
Likelihood
—MITRE likelihood of exploit

Last updated:

What is CWE-441?

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 allowed service, but the request could contain disallowed directives, commands, or resources.

CWE-441 is a class-level weakness in MITRE’s Common Weakness Enumeration. Applicable platforms: Not Language-Specific; Not OS-Specific; Not Architecture-Specific; Not Technology-Specific.

Source: MITRE CWE (CWE-441 definition, reproduced verbatim). Counts and linkage below are Threadlinqs data.

Consequences

  • Non-Repudiation, Access Control — Gain Privileges or Assume Identity, Hide Activities, Execute Unauthorized Code or Commands

Source: MITRE CWE, common consequences.

How CWE-441 is exploited in the wild

Threadlinqs maps 14 CVEs to CWE-441, published between 2026-07-23 and 2026-11-10. 1 is listed in CISA’s Known Exploited Vulnerabilities catalog, the authoritative record of exploitation in the wild. By CVSS v3 severity the set splits into 6 critical, 5 high, 1 medium. The highest EPSS score in the set is 0.4% (CVE-2026-69399), the modelled probability of exploitation in the next 30 days. 21 tracked threats reference CWE-441 directly or through a CVE it covers; the most recent is “Microsoft Patch Tuesday November 2026: ~1,095 vulnerabilities, 64 critical, one exploited Outlook NTLM-leak spoofing zero-day (CVE-2026-124194)” (2026-11-11). Affected products concentrate in AsyncHttpClient (2), Google (2), Microsoft (2), among 12 vendors in total.

Vulnerabilities (CVEs)

All 14 CVEs mapped to CWE-441, CISA KEV first, then by CVSS score.

Affected vendors

Threat activity

21 tracked threats cite CWE-441:

Mitigations

  • 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.

Source: MITRE CWE, potential mitigations.

Detection methods (MITRE CWE)

  • Automated Static Analysis: Automated static analysis, commonly referred to as Static Application Security Testing (SAST), can find some instances of this weakness by analyzing source code (or binary/compiled code) without having to execute it. Typically, this is done by building a model of data flow and control flow, then searching for potentially-vulnerable patterns that connect "sources" (origins of input) with "sinks" (destinations where the data interacts with external components, a lower layer such as the OS, etc.)

Source: MITRE CWE, detection methods. Threadlinqs detection rules for the threats above are Blue tier and higher.