Security Resilience

CVE-2026-95311

Google Chrome ≤ 154.0.8037.57

Published
29 September 2026
Modified
30 September 2026
Patch / advisory
View advisory
CVSS Score v3.1 9.6
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS Score 0.0046 39th percentile
Risk Priority 68 floored blend · peak EPSS

CVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). Risk Priority is our own derived reading, not an NVD score.

Summary

CVE-2026-95311 is a critical-severity Free of Memory not on the Heap (CWE-590) vulnerability in Google Chrome. Its CVSS base score is 9.6 (Critical).

Operationally, exploitation aligns with the MITRE ATT&CK technique Junk Data (T1001.001); ranked at the 39th 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

Free of non-heap memory in Fonts in Google Chrome prior to 154.0.8037.57 allowed a remote attacker leveraging social engineering to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

CWE(s)
CWE-590

Related Threats

MITRE ATT&CK Enterprise Techniques

T1001.001 Junk Data Command And Control
Adversaries may add junk data to protocols used for command and control to make detection more difficult.
attack.mitre.org →
T1001.003 Protocol or Service Impersonation Command And Control
Adversaries may impersonate legitimate protocols or web service traffic to disguise command and control activity and thwart analysis efforts.
attack.mitre.org →
T1003 OS Credential Dumping Credential Access
Adversaries may attempt to dump credentials to obtain account login and credential material, normally in the form of a hash or a clear text password.
attack.mitre.org →
T1003.002 Security Account Manager Credential Access
Adversaries may attempt to extract credential material from the Security Account Manager (SAM) database either through in-memory techniques or through the Windows Registry where the SAM database is stored.
attack.mitre.org →
T1003.005 Cached Domain Credentials Credential Access
Adversaries may attempt to access cached domain credentials used to allow authentication to occur in the event a domain controller is unavailable.
attack.mitre.org →
T1003.006 DCSync Credential Access
Adversaries may attempt to access credentials and other sensitive information by abusing a Windows Domain Controller's application programming interface (API)(Citation: Microsoft DRSR Dec 2017) (Citation: Microsoft GetNCCChanges) (Citati…
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2024-8636Same product: Google Chrome
CVE-2026-11061Same product: Google Chrome
CVE-2024-8198Same product: Google Chrome
CVE-2024-7534Same product: Google Chrome
CVE-2026-10999Same product: Google Chrome
CVE-2026-14420Same product: Google Chrome
CVE-2026-15114Same product: Google Chrome
CVE-2023-4072Same product: Google Chrome
CVE-2024-6102Same product: Google Chrome
CVE-2026-14422Same product: Google Chrome

Affected Assets

google
chrome
≤ 154.0.8037.57

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation partial match

Developer testing and evaluation (static/dynamic analysis) can discover incorrect free() calls on non-heap memory.

SA-15 Development Process, Standards, and Tools partial match

Documented development standards and tools can require correct heap allocation/deallocation discipline, stopping the defect at introduction.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 partial match
blocks

Secure SDLC practices directly prevent incorrect free() calls via code review, static analysis, and developer training.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.25 Secure development life cycle partial match
blocks

Secure development lifecycle mandates memory-safety practices that reduce use-after-free and invalid-free bugs.

A.8.26 Application security requirements partial match
removes
A.8.27 Secure system architecture and engineering principles partial match
blocks

A.8.27 mandates establishing and applying secure engineering principles (including secure-by-design, least privilege, hardening, and design reviews) but does not itself stop a free() of non-heap memory from being exploitable; the weakness can still be present and reached at runtime.

A.8.28 Secure coding partial match
prevents

Secure coding standards explicitly forbid freeing pointers not obtained from heap allocators, directly mitigating CWE-590.

A.8.29 Security testing in development and acceptance partial match
finds

Security testing in development can detect invalid-free defects before release.

A.8.8 Management of technical vulnerabilities partial match
removes

References