CWE · MITRE source
CWE-204Observable Response Discrepancy
The product provides different responses to incoming requests in a way that reveals internal state information to an unauthorized actor outside of the intended control sphere.
Last updated: 22 August 2026 14:14 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: partial · 5 mapping(s) from 2 framework(s): CAPEC 4 (partial) · ATT&CK 1 (partial)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls that address this weakness (2)AI-assisted
| Control | Title | Family | Why it addresses this CWE |
|---|---|---|---|
SC-30 | Concealment and Misdirection | SC | Fake or randomized responses remove distinguishable success/failure signals attackers rely on. |
SI-11 | Error Handling | SI | Eliminates distinguishable response discrepancies in error conditions that could be exploited for reconnaissance. |
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-25350 UPD | 7.3 | 9.8 | 0.0043 | 2026-05-23 |
CVE-2026-15747 | 6.7 | 9.1 | 0.0026 | 2026-07-14 |
CVE-2025-5485 UPD | 6.5 | 8.6 | 0.0041 | 2025-06-12 |
CVE-2026-69519 | 6.3 | 8.6 | 0.0058 | 2026-08-20 |
CVE-2021-20049 UPD | 6.1 | 7.5 | 0.0135 | 2021-12-23 |
CVE-2021-34580 UPD | 6.0 | 7.5 | 0.0103 | 2021-10-27 |
CVE-2025-3092 UPD | 5.8 | 7.5 | 0.0041 | 2025-06-24 |
CVE-2025-46390 UPD | 5.8 | 7.5 | 0.0031 | 2025-08-06 |
CVE-2025-12455 UPD | 5.8 | 7.5 | 0.0030 | 2026-03-13 |
CVE-2026-33419 UPD | 5.8 | 7.5 | 0.0039 | 2026-03-24 |
CVE-2026-27462 | 5.8 | 7.5 | 0.0031 | 2026-08-21 |
CVE-2022-41697 UPD | 5.7 | 5.3 | 0.2020 | 2022-12-22 |
CVE-2026-60007 | 5.6 | 7.4 | 0.0038 | 2026-08-04 |
CVE-2026-4113 UPD | 5.4 | 7.2 | 0.0036 | 2026-04-09 |
CVE-2016-9499 UPD | 5.3 | 5.3 | 0.0777 | 2018-07-13 |
CVE-2021-38476 UPD | 5.3 | 6.5 | 0.0078 | 2021-10-19 |
CVE-2022-39315 UPD | 5.2 | 6.5 | 0.0061 | 2022-10-25 |
CVE-2023-46170 UPD | 5.1 | 6.5 | 0.0045 | 2024-03-07 |
CVE-2025-61907 UPD | 5.1 | 6.5 | 0.0037 | 2025-10-16 |
CVE-2025-66307 | 5.1 | 6.5 | 0.0031 | 2025-12-01 |
CVE-2024-24766 UPD | 5.0 | 6.2 | 0.0076 | 2024-03-06 |
CVE-2024-28232 UPD | 5.0 | 6.2 | 0.0062 | 2024-04-01 |
CVE-2025-67874 | 5.0 | 6.5 | 0.0035 | 2025-12-16 |
CVE-2026-34264 UPD | 5.0 | 6.5 | 0.0027 | 2026-04-14 |
CVE-2019-19030 UPD | 4.8 | 5.3 | 0.0189 | 2022-12-26 |