CVE-2025-0762
Memory Safety in Google Chrome ≤ 132.0.6834.159
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-0762 is a high-severity Use After Free (CWE-416) vulnerability in Google Chrome. Its CVSS base score is 8.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Client Execution (T1203); ranked at the 26th 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 CM-11 (User-installed Software) and SI-2 (Flaw Remediation) — 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-0762 is a use-after-free vulnerability (CWE-416) in the DevTools component of Google Chrome prior to version 132.0.6834.159. This flaw allows a remote attacker to potentially exploit heap corruption via a crafted Chrome Extension. 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 Medium severity by Chromium security.
A remote attacker with no privileges can exploit this vulnerability by convincing a user to interact with a maliciously crafted Chrome Extension, such as through installation or usage triggered by a webpage. Successful exploitation could result in heap corruption, enabling high-impact compromise of confidentiality, integrity, and availability, potentially leading to arbitrary code execution within the browser context.
Google has mitigated this vulnerability in Chrome stable channel version 132.0.6834.159. Security practitioners should advise users to update immediately to this version or later. Additional details are available in the Chrome Releases announcement at https://chromereleases.googleblog.com/2025/01/stable-channel-update-for-desktop_28.html and the Chromium issue tracker at https://issues.chromium.org/issues/384844003.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-1856
Vulnerability Data
Use after free in DevTools in Google Chrome prior to 132.0.6834.159 allowed a remote attacker to potentially exploit heap corruption via a crafted Chrome Extension. (Chromium security severity: Medium)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
UAF in Chrome DevTools enables RCE via crafted malicious extension (client-side exploitation).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly mitigates the use-after-free vulnerability by requiring timely remediation through patching Chrome to version 132.0.6834.159 or later.
Prevents exploitation by enforcing organizational controls on user-installed software, blocking or monitoring installation of crafted malicious Chrome Extensions.
Implements memory safeguards such as address space layout randomization or data execution prevention to mitigate heap corruption from use-after-free in DevTools.
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.
Secure SDLC practices directly incorporate memory-safety tooling and reviews that prevent most use-after-free defects.
Vulnerability identification processes can discover use-after-free issues via scanning or analysis but do not prevent their introduction.
Routine patching removes known use-after-free instances after they have been introduced in released software.
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.
Security testing in development can detect use-after-free bugs before release.
Secure SDLC mandates memory-safety practices that reduce use-after-free defects.
Application security requirements can specify memory-management rules that mitigate use-after-free.
Secure architecture principles include memory-safety design choices that limit use-after-free exposure.
Secure coding standards directly prescribe avoidance of use-after-free patterns.
Change-management processes help ensure memory-safety fixes are deployed consistently.