CWE · MITRE source
CWE-441Unintended Proxy or Intermediary ('Confused Deputy')
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:
Last updated: 14 October 2026 20:41 UTC
OWASP Top 10 for Web (2025)
This weakness contributes to A01:2025 Broken Access Control.
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
—
—
—
NIST 800-53 r5 controls PROPOSED for this weakness (1)AI-assisted
These are model PROPOSALS, not graded mappings. They come
from controls_to_cwe_proposals, which carries no grade field at
all; across the CWE pages 1,540 of 1,722 such associations (89%) have never
been graded by anything. The heading said “address” until
2026-09-29, which asserted a relationship the data does not carry.
Graded cross-walks are on the framework map, not here.
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-32 | System Partitioning | SC | Mitigates confused deputy risks by ensuring distinct privilege domains so one partition cannot unintentionally act on behalf of another. |
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2026-83548 KEV | 10.0 | 10.0 | 0.0804 | 2026-09-01 |
CVE-2025-47269 UPD | 8.2 | 8.3 | 0.4286 | 2025-05-09 |
CVE-2021-20042 UPD | 7.8 | 9.8 | 0.0368 | 2021-12-08 |
CVE-2026-39906 UPD | 7.5 | 10.0 | 0.0088 | 2026-04-14 |
CVE-2026-23751 | 7.5 | 9.8 | 0.0088 | 2026-04-23 |
CVE-2026-42933 | 7.4 | 10.0 | 0.0051 | 2026-07-23 |
CVE-2026-69399 UPD | 7.4 | 10.0 | 0.0048 | 2026-09-17 |
CVE-2026-102255 | 7.4 | 10.0 | 0.0048 | 2026-10-07 |
CVE-2025-62718 UPD | 7.3 | 9.9 | 0.0119 | 2026-04-09 |
CVE-2015-2947 UPD | 7.2 | 9.1 | 0.0150 | 2017-04-13 |
CVE-2025-64123 UPD | 7.2 | 9.8 | 0.0032 | 2026-01-02 |
CVE-2026-94205 | 7.2 | 9.8 | 0.0036 | 2026-10-06 |
CVE-2026-72526 UPD | 7.1 | 9.9 | 0.0070 | 2026-08-12 |
CVE-2019-3924 UPD | 7.0 | 7.5 | 0.1570 | 2019-02-20 |
CVE-2026-67567 UPD | 7.0 | 9.9 | 0.0062 | 2026-08-20 |
CVE-2026-100706 | 7.0 | 9.9 | 0.0061 | 2026-09-26 |
CVE-2026-7381 UPD | 6.9 | 9.1 | 0.0052 | 2026-04-29 |
CVE-2022-39361 UPD | 6.8 | 8.8 | 0.0107 | 2022-10-26 |
CVE-2026-70398 UPD | 6.8 | 9.6 | 0.0052 | 2026-08-12 |
CVE-2026-53513 | 6.7 | 9.6 | 0.0025 | 2026-07-15 |
CVE-2025-25306 UPD | 6.5 | 9.3 | 0.0018 | 2025-03-10 |
CVE-2026-36608 UPD | 6.5 | 8.8 | 0.0030 | 2026-06-03 |
CVE-2026-44494 UPD | 6.4 | 8.7 | 0.0093 | 2026-06-11 |
CVE-2026-44945 UPD | 6.4 | 9.1 | 0.0056 | 2026-08-05 |
CVE-2026-103922 | 6.4 | 9.3 | 0.0021 | 2026-10-01 |