Cyber Resilience

CVE-2025-1920

Memory Safety in Google Chrome ≤ 134.0.6998.88

Memory Safety
Published
10 March 2025
Modified
07 April 2025
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.0032 24th percentile
Risk Priority 63 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-2025-1920 is a high-severity Type Confusion (CWE-843) 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 at the 24th 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.

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-1920 is a type confusion vulnerability (CWE-843) in the V8 JavaScript engine within Google Chrome versions prior to 134.0.6998.88. This flaw enables a remote attacker to potentially trigger heap corruption by means of a crafted HTML page. The issue has 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.

A remote attacker without privileges can exploit this vulnerability by luring a user into interacting with a malicious site, such as by visiting a crafted HTML page. Successful exploitation could grant high-level impacts on confidentiality, integrity, and availability, potentially allowing heap corruption that leads to arbitrary code execution or other severe compromises within the browser context.

Google has addressed the vulnerability in Chrome stable channel version 134.0.6998.88 and later, as announced in the stable channel update for desktop (https://chromereleases.googleblog.com/2025/03/stable-channel-update-for-desktop_10.html). Further technical details are available in the associated Chromium issue tracker (https://issues.chromium.org/issues/398065918). Security practitioners should prioritize updating affected Chrome installations to mitigate this risk.

EU & UK References

Vulnerability Data

Type Confusion in V8 in Google Chrome prior to 134.0.6998.88 allowed a remote attacker to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: High)

CWE(s)
CWE-843

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 →
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-2023-4068Same product: Google Chrome
CVE-2023-4069Same product: Google Chrome
CVE-2026-17989Same product: Google Chrome
CVE-2023-0703Same product: Google Chrome
CVE-2024-12381Same product: Google Chrome
CVE-2026-17948Same product: Google Chrome
CVE-2026-17687Same product: Google Chrome
CVE-2023-2935Same product: Google Chrome
CVE-2024-12053Same product: Google Chrome
CVE-2024-8904Same product: Google Chrome

Affected Assets

google
chrome
≤ 134.0.6998.88

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.5.2
  • V3.2.3
  • V15.3.5

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and type-aware analysis) directly finds type-confusion flaws before deployment.

SA-8 Security and Privacy Engineering Principles partial match

Engineering principles can require use of type-safe languages, static typing, and runtime type checks that structurally avoid allocating one type and accessing another.

SI-16 Memory Protection partial match

Memory-protection controls limit the blast radius when a type-confusion access occurs but do not stop the flaw itself.

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 SDLC practices directly prevent type-confusion flaws via safe typing, static analysis, and code review while the control itself addresses many additional weaknesses.

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 can detect type-confusion vulnerabilities through fuzzing and static analysis.

A.8.25 Secure development life cycle partial match
prevents

Secure SDLC mandates type-safe design and review that can catch type-confusion flaws.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify strong typing and interface contracts that reduce type confusion.

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

Secure architecture principles promote type-safe languages and memory-safety mechanisms that mitigate type confusion.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly forbid unsafe type casts and require static-analysis checks for type confusion.

References