CVE-2026-112992
Google Chrome ≤ 156.0.8078.47
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2026-112992 is a critical-severity Observable Discrepancy (CWE-203) vulnerability in Google Chrome. Its CVSS base score is 9.6 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Gather Victim Identity Information (T1589); ranked at the 29th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to IA-6 (Authentication Feedback) and SI-11 (Error Handling) — see the control section below for these in your framework.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-105565
Vulnerability Data
Observable discrepancy in Canvas in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to leak cross-origin data via a crafted HTML page. (Chromium security severity: Medium)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
- 1 hardening rule · 1 OS baseline
—
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Obscures authentication feedback so that success/failure differences are not observable to attackers.
Requires error messages to avoid revealing exploitable details, directly stopping observable response discrepancies.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
Secure SDLC practices directly prevent observable response discrepancies via consistent error handling and timing.
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
Training helps developers recognize that uniform error messages, constant-time comparisons and non-leaking response patterns are security requirements, addressing the common knowledge-gap cases (error-message enumeration, basic auth timing); however, CWE-203 also covers deeper technical instances — cache/power/microarchitectural side channels, TTL and packet-level discrepancies — that exceed what general awareness training reaches, leaving a nameable remainder.
Secure coding standards can mandate consistent error messages, constant-time comparisons, and uniform response behavior, addressing the application-layer observable discrepancies (different error messages, response timing in auth flows). The remainder is nameable: hardware-level side channels (cache, power consumption, RAPL interfaces), subtle timing differences emerging from complex code paths, and network-level observable differences (TTL, packet behavior) are not caught by coding practice alone, and the clause's mechanism is human practice which is fallible.
A.8.30 carries its effect through the secure design, coding and testing practices (8.25-8.29) its contract requires of the supplier, so observable discrepancies in delivered code are reduced the way those practices reduce them — but the clause mandates a practice, not a mechanism, and what it catches depends on the rigour of the supplier's implementation, leaving a fallible remainder.
A.8.5's log-on procedure guidance (items c, d, e) directly blocks user enumeration via error messages and timing discrepancies during authentication, but the control does not address observable discrepancies outside the log-on process such as side-channel attacks or behavioral information leaks.