CWE · MITRE source
CWE-201Insertion of Sensitive Information Into Sent Data
The code transmits data to another actor, but a portion of the data includes sensitive information that should not be accessible to that actor.
Last updated: 20 November 2026 11:24 UTC
Cumulative inbound coverage
How completely the frameworks we cross-walk collectively cover this — the verdict is the strongest single mapping (overlapping partials are not summed); breadth shows the corroboration behind it.
Collective: full · 54 mapping(s) from 5 framework(s): ATT&CK 33 (full) · ISO_IEC_27002_2022 13 (mostly) · 4 (mostly) · 800-53 3 (full) · ASVS 5.0 1 (full)
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.
DE.CM-09
- 1 hardening rule · 1 OS baseline
V14.2.3
NIST 800-53 r5 controls PROPOSED for this weakness (1)
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 |
|---|---|---|---|
SI-20 | Tainting | SI | Embedding taints allows detection when sensitive data is inserted into outbound or sent data streams. |
MITRE ATT&CK techniques this weakness enables
Our own two-way CWE↔ATT&CK cross-walk — a direct mapping with no public source (the CWE→CAPEC→ATT&CK chain leaves most top weaknesses, incl. XSS and SQLi, mapped to nothing).
Direction: ← other covers this;
→ this covers other (F/M/P = full / mostly /
partial). gov = governs / implements (a mandate, not coverage).
Top CVEs of this weakness type, ranked by Risk Priority
| CVE | Risk | CVSS | EPSS | Published |
|---|---|---|---|---|
CVE-2018-17245 UPD | 7.6 | 9.8 | 0.0152 | 2018-12-20 |
CVE-2020-26085 UPD | 7.4 | 9.9 | 0.0232 | 2021-01-07 |
CVE-2025-49408 UPD | 7.4 | 10.0 | 0.0053 | 2025-08-20 |
CVE-2026-123551 UPD | 7.4 | 10.0 | 0.0041 | 2026-11-08 |
CVE-2020-27134 UPD | 7.3 | 9.9 | 0.0167 | 2020-12-11 |
CVE-2026-92555 | 7.3 | 9.8 | 0.0037 | 2026-10-08 |
CVE-2020-27127 UPD | 7.2 | 9.9 | 0.0135 | 2020-12-11 |
CVE-2020-27132 UPD | 7.2 | 9.9 | 0.0145 | 2020-12-11 |
CVE-2020-27133 UPD | 7.2 | 9.9 | 0.0114 | 2020-12-11 |
CVE-2026-86413 UPD | 7.0 | 9.1 | 0.0073 | 2026-10-20 |
CVE-2026-86414 UPD | 7.0 | 9.1 | 0.0068 | 2026-10-20 |
CVE-2026-87861 UPD | 7.0 | 9.1 | 0.0068 | 2026-10-20 |
CVE-2026-39912 UPD | 6.9 | 9.1 | 0.0061 | 2026-04-09 |
CVE-2026-42880 UPD | 6.9 | 9.6 | 0.0065 | 2026-05-07 |
CVE-2026-8924 UPD | 6.9 | 9.1 | 0.0066 | 2026-07-03 |
CVE-2026-106501 | 6.9 | 9.6 | 0.0059 | 2026-10-06 |
CVE-2025-41118 UPD | 6.8 | 9.1 | 0.0041 | 2026-04-15 |
CVE-2026-52394 | 6.8 | 9.1 | 0.0040 | 2026-10-13 |
CVE-2026-88811 | 6.8 | 9.1 | 0.0043 | 2026-11-02 |
CVE-2025-58098 UPD | 6.6 | 8.3 | 0.0153 | 2025-12-05 |
CVE-2023-48240 UPD | 6.5 | 9.0 | 0.0071 | 2023-11-20 |
CVE-2025-48749 UPD | 6.4 | 9.1 | 0.0045 | 2025-05-28 |
CVE-2025-60188 UPD | 6.4 | 7.5 | 0.0373 | 2025-11-06 |
CVE-2026-86409 UPD | 6.3 | 8.1 | 0.0110 | 2026-10-20 |
CVE-2026-87862 UPD | 6.3 | 8.1 | 0.0100 | 2026-10-20 |