Security Resilience

CVE-2026-106304

Memory Safety in Google Chrome ≤ 155.0.8059.39

Published
06 October 2026
Modified
07 October 2026
Patch / advisory
CVSS Score v3.1 4.7
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:N
EPSS Score 0.0020 10th percentile
Risk Priority 37 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-106304 is a medium-severity Out-of-bounds Read (CWE-125) vulnerability in Google Chrome. Its CVSS base score is 4.7 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Endpoint Denial of Service (T1499); ranked at the 10th 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-8 (Security and Privacy Engineering Principles) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

Out of bounds read in ANGLE in Google Chrome prior to 155.0.8059.39 allowed a remote attacker to read memory outside 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

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.
T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
T1185 Browser Session Hijacking Collection
Adversaries may take advantage of security vulnerabilities and inherent functionality in browser software to change content, modify user-behaviors, and intercept information as part of various browser session hijacking techniques.
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.
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.
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2023-0698Same product: Google Chrome
CVE-2026-79020Same product: Google Chrome
CVE-2026-87604Same product: Google Chrome
CVE-2026-14406Same product: Google Chrome
CVE-2026-14011Same product: Google Chrome
CVE-2026-10985Same product: Google Chrome
CVE-2026-17745Same product: Google Chrome
CVE-2026-17801Same product: Google Chrome
CVE-2026-87650Same product: Google Chrome
CVE-2026-9895Same product: Google Chrome

Affected Assets

google
chrome
≤ 155.0.8059.39

Mitigating Controls

Mitigating Controls (NIST 800-53 r5)

Our mappings, made for this CVE.

Developer testing and evaluation directly finds out-of-bounds read flaws through static analysis, fuzzing, and dynamic bounds checks.

Secure engineering principles require bounds checking and memory-safe constructs that stop out-of-bounds reads from being introduced.

Input validation rejects malformed indices or lengths that would otherwise cause reads outside buffer bounds.

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-development practices such as bounds checking and memory-safe languages directly prevent out-of-bounds reads.

ID.RA-01 partial match
blocks

Vulnerability scanning and recording can discover instances of out-of-bounds reads after code is deployed.

PR.PS-02 partial match
blocks

Routine patching replaces vulnerable code containing out-of-bounds read flaws.

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 includes fuzzing and static analysis that detect out-of-bounds read defects before release.

finds

A.5.26's post-incident root cause analysis (item i) and vulnerability identification (item j) explicitly aim to find the specific weakness that caused an incident, so OOB reads that triggered observable incidents (crashes, data leaks) are identified through forensic and root-cause work; however, only a minority of latent OOB reads in deployed code cause observable incidents, leaving the bulk of the class outside this incident-driven reach.

prevents

A.6.3's education and training of technical teams can raise developer awareness of memory-safety practices (bounds checking, length validation) and reduce some out-of-bounds read introductions, but training is fallible and the strongest controls for this implementation-phase defect are secure coding (A.8.28) and security testing (A.8.29), so the effect is a minority one.

prevents

Secure coding standards explicitly forbid unsafe pointer arithmetic and mandate bounds-checked reads, eliminating CWE-125.

finds

A.8.8's reach is DISCLOSURE — it surfaces OOB reads only where they appear as published CVEs in third-party components in the asset inventory. CWE-125 commonly surfaces as CVEs (Heartbleed, kernel/IP-stack bugs), so a real share is found, but first-party OOB reads and un-disclosed instances are outside the clause's reach, capping the rung at `partial`.

References