CVE-2026-113030
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-113030 is a high-severity Use of Uninitialized Variable (CWE-457) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Drive-by Compromise (T1189); ranked at the 42th 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 SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-105653
Vulnerability Data
Use of uninitialized variable in V8 in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code inside the sandbox 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
Mitigating Controls (NIST 800-53 r5)
Our mappings, made for this CVE.
Developer testing and static analysis directly find uses of uninitialized variables before deployment.
Documented development standards and tools can enforce initialization requirements in code.
Engineering principles can mandate explicit variable initialization to avoid uninitialized use.
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 catch uninitialized-variable defects via static analysis and code review while the control encompasses many additional development controls.
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.
Security testing can detect uninitialized-variable bugs, but the control is broader.
Training developers in secure coding practices (the technical-team portion of A.6.3) reduces uninitialized-variable defects, but the weakness is a subtle coding mistake that even trained developers introduce, so the effect is a minority one — consistent with the A.8.28 vs CWE-502 anchor at the same rung.
Secure coding explicitly requires variable initialization and static-analysis checks.
A.8.8's reach is disclosure-based (vulnerability scanning, published advisories, third-party inventory); CWE-457 is a first-party code defect whose bulk lives in custom code that never receives a CVE, so only the minority of disclosed instances are surfaced — the same shape as A.8.8 -> CWE-89.