Security Resilience

CVE-2026-113315

Google Chrome ≤ 156.0.8078.47

Published
20 October 2026
Modified
03 November 2026
Patch / advisory
CVSS Score v3.1 8.8
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS Score 0.0040 35th percentile
Risk Priority 64 floored blend · peak EPSS

CVSS 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-113315 is a high-severity Use of Uninitialized Resource (CWE-908) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 35th 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.

EU & UK References

Vulnerability Data

Uninitialized resource in ANGLE in Google Chrome prior to 156.0.8078.47 allowed a remote attacker who had compromised the renderer process to read memory 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

T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
T1499 Endpoint Denial of Service Impact
Adversaries may perform Endpoint Denial of Service (DoS) attacks to degrade or block the availability of services to users.
T1499.004 Application or System Exploitation Impact
Adversaries may exploit software vulnerabilities that can cause an application or system to crash and deny availability to users.
T1189 Drive-by Compromise Initial Access
Adversaries may gain access to a system through a user visiting a website over the normal course of browsing.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-113140Same product: Google Chrome
CVE-2026-118354Same product: Google Chrome
CVE-2026-102300Same product: Google Chrome
CVE-2026-106386Same product: Google Chrome
CVE-2026-95293Same product: Google Chrome
CVE-2026-121176Same product: Google Chrome
CVE-2026-95324Same product: Google Chrome
CVE-2026-113031Same product: Google Chrome
CVE-2026-113143Same product: Google Chrome
CVE-2026-102319Same product: Google Chrome

Affected Assets

google
chrome
≤ 156.0.8078.47

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation (including static analysis) can find uses of uninitialized resources after they are coded.

Requiring documented development standards and tools can mandate initialization checks and safe patterns that stop the weakness from being introduced.

Engineering principles can require explicit resource initialization before use, structurally avoiding uninitialized access.

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.

PR.PS-06 mostly match
blocks

Secure SDLC activities such as static analysis and code review directly prevent use of uninitialized resources while also addressing many other weaknesses.

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.

finds

Security testing in development and acceptance can detect uninitialized resource usage through dynamic analysis and fuzzing.

prevents

Secure coding standards directly require explicit initialization of all variables and resources, substantially mitigating CWE-908.

prevents

A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25–8.29), so it reduces ordinary implementation-phase software weaknesses like CWE-908 the way those practices do, but only partially because the clause depends on the supplier actually implementing secure coding and the practice is fallible; A.8.30 carries a declared ceiling of `partial` on this verb.

finds

A.8.8's reach is disclosure-based: it finds vulnerabilities that have been published as advisories or surface in third-party component inventories. CWE-908 does commonly appear as CVEs (multiple observed examples), so A.8.8 finds a minority of instances through that channel, while the bulk of uninitialized-resource defects in first-party code remain outside its reach.

References