CVE-2026-113012
Google Chrome ≤ 156.0.8078.47
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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-113012 is a high-severity Incomplete Cleanup (CWE-459) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Unsecured Credentials (T1552); ranked at the 43th 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 AC-12 (Session Termination) and SA-11 (Developer Testing and Evaluation) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-105457
Vulnerability Data
Incomplete cleanup in GPU in Google Chrome prior to 156.0.8078.47 allowed a remote attacker who had compromised the renderer process to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V6.4.1
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Session termination forces explicit release of session-related temporary resources.
Developer testing and evaluation can discover incomplete cleanup through dynamic analysis or resource-leak testing.
Preventing unintended information transfer through shared resources requires complete cleanup of those resources.
Non-persistence mechanisms explicitly initiate resources in a known state and terminate them, directly enforcing cleanup.
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-development practices and coding standards normally require proper resource release and cleanup.
Life-cycle management encompasses disposal of temporary resources but does not specifically target runtime cleanup bugs.
Explicitly calls for removing sensitive data after use, directly addressing one class of incomplete cleanup.
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.
A.8.29's source reach (code review, static analysis) catches the bulk of CWE-459 instances — unclosed streams, missing finally blocks, and leftover temp files are well-detected code patterns — but a nameable remainder of subtle cases (cleanup dependent on specific error paths, alternate data streams, conditions only observable at runtime) escapes automated detection and requires deeper analysis or specific runtime triggering.
Secure-coding rules can mandate explicit cleanup of temporary resources, but do not guarantee it.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software implementation weaknesses like incomplete cleanup in delivered code the way those practices do, at `partial` -- the same reading that graded A.8.30 -> CWE-134 `partial` and that sits at the clause's declared ceiling.
Change-management processes may require cleanup verification, but the control itself does not address the weakness.