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: 16 October 2026 10:19 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 · 1 mapping(s) from 1 framework(s): ATT&CK 1 (partial)
Control responseHuman-reviewed
Answering this weakness across the control lifecycle, from our framework cross-walks.
NIST 800-53 r5 controls PROPOSED for this weakness (2)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 |
|---|---|---|---|
SI-11 | Error Handling | SI | graded mostly Eliminates distinguishable response discrepancies in error conditions that could be exploited for reconnaissance. |
SC-30 | Concealment and Misdirection | SC | Fake or randomized responses remove distinguishable success/failure signals attackers rely on. |
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.0025 | 2026-07-14 |
CVE-2025-5485 UPD | 6.5 | 8.6 | 0.0043 | 2025-06-12 |
CVE-2026-69519 | 6.4 | 8.6 | 0.0103 | 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.0104 | 2021-10-27 |
CVE-2026-111235 | 6.0 | 9.1 | 0.0000 | 2026-10-15 |
CVE-2025-3092 UPD | 5.9 | 7.5 | 0.0047 | 2025-06-24 |
CVE-2026-33419 UPD | 5.9 | 7.5 | 0.0054 | 2026-03-24 |
CVE-2025-46390 UPD | 5.8 | 7.5 | 0.0031 | 2025-08-06 |
CVE-2025-12455 UPD | 5.8 | 7.5 | 0.0031 | 2026-03-13 |
CVE-2026-27462 UPD | 5.8 | 7.5 | 0.0043 | 2026-08-21 |
CVE-2026-19080 | 5.8 | 7.5 | 0.0030 | 2026-09-04 |
CVE-2022-41697 UPD | 5.7 | 5.3 | 0.2004 | 2022-12-22 |
CVE-2026-60007 | 5.7 | 7.4 | 0.0055 | 2026-08-04 |
CVE-2026-19205 | 5.7 | 7.5 | 0.0024 | 2026-09-04 |
CVE-2026-4113 UPD | 5.5 | 7.2 | 0.0060 | 2026-04-09 |
CVE-2021-38476 UPD | 5.3 | 6.5 | 0.0078 | 2021-10-19 |
CVE-2022-39315 UPD | 5.3 | 6.5 | 0.0066 | 2022-10-25 |
CVE-2016-9499 UPD | 5.2 | 5.3 | 0.0767 | 2018-07-13 |
CVE-2023-46170 UPD | 5.1 | 6.5 | 0.0045 | 2024-03-07 |
CVE-2025-61907 UPD | 5.1 | 6.5 | 0.0040 | 2025-10-16 |
CVE-2025-66307 UPD | 5.1 | 6.5 | 0.0032 | 2025-12-01 |
CVE-2026-34264 UPD | 5.1 | 6.5 | 0.0039 | 2026-04-14 |
CVE-2026-86758 UPD | 5.1 | 6.5 | 0.0041 | 2026-09-09 |