Cyber Resilience

CVE-2025-9132

Memory Safety in Google Chrome ≤ 139.0.7258.138

Memory Safety
Published
20 August 2025
Modified
17 June 2026
Patch / advisory
View 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.030 86th percentile
Risk Priority 69 floored blend · peak EPSS

Summary

CVE-2025-9132 is a high-severity Out-of-bounds Write (CWE-787) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 14% of CVEs by exploit likelihood; 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.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2025-9132 is an out-of-bounds write vulnerability (CWE-787) in the V8 JavaScript and WebAssembly engine within Google Chrome versions prior to 139.0.7258.138. This flaw enables potential heap corruption when processing a crafted HTML page. The issue carries a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) and is rated High severity by Chromium security standards. It was published on 2025-08-20.

A remote attacker can exploit this vulnerability by tricking a user into visiting a malicious website containing a specially crafted HTML page. No user privileges or special access are required beyond the victim's interaction, such as clicking a link or loading the page. Successful exploitation could lead to heap corruption, potentially allowing arbitrary code execution, data tampering, or system compromise with high impacts on confidentiality, integrity, and availability.

Mitigation is addressed in the Google Chrome stable channel update to version 139.0.7258.138 and later, as detailed in the Chrome Releases blog post at https://chromereleases.googleblog.com/2025/08/stable-channel-update-for-desktop_19.html. Additional technical details are available in the Chromium issue tracker at https://issues.chromium.org/issues/436181695. Security practitioners should prioritize updating affected Chrome installations.

EU & UK References

Vulnerability Data

Out of bounds write in V8 in Google Chrome prior to 139.0.7258.138 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CWE(s)
CWE-787

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
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.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1211 Exploitation for Stealth Stealth
Adversaries may exploit vulnerabilities to evade detection by hiding activity, suppressing logging, or operating within trusted or unmonitored components.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2016-5198Same product: Apple Macos
CVE-2024-49513Same product: Apple Macos
CVE-2023-1217Same product: Google Chrome
CVE-2012-0754Same product: Linux Linux Kernel
CVE-2024-43760Same product: Apple Macos
CVE-2025-43593Same product: Apple Macos
CVE-2023-21576Same product: Apple Macos
CVE-2025-21130Same product: Apple Macos
CVE-2024-45152Same product: Apple Macos
CVE-2025-43590Same product: Apple Macos

Affected Assets

google
chrome
≤ 139.0.7258.138

Mitigating Controls

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and bounds checks) finds out-of-bounds write flaws before deployment.

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

Requiring documented secure-development standards and tools can mandate bounds-checked coding practices that avoid the weakness.

SI-10 Information Input Validation partial match

Input validation can structurally reject or sanitize data that would otherwise trigger an out-of-bounds write.

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the exploitability and blast radius of a successful out-of-bounds write.

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 mostly match
prevents

Secure-development practices (static analysis, bounds checking, code review) are the primary means of preventing out-of-bounds writes.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover out-of-bounds write flaws so they can be remediated.

PR.PS-02 partial match
prevents

Patching or replacing vulnerable software directly eliminates known instances of this coding weakness.

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.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect and prevent out-of-bounds write defects.

A.8.25 Secure development life cycle partial match
prevents

Secure development life cycle mandates practices that prevent out-of-bounds writes.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify bounds-checking and safe memory handling.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles reduce the likelihood of buffer overflows.

A.8.28 Secure coding partial match
prevents

Secure coding directly addresses out-of-bounds writes through language choice and coding standards.

A.8.32 Change management partial match
prevents

Change management can enforce review gates that catch unsafe memory operations before deployment.

References