CVE-2025-13720
Google Chrome ≤ 143.0.7499.40
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2025-13720 is a high-severity Incorrect Type Conversion or Cast (CWE-704) 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 18th 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.
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-13720 is a bad cast vulnerability (CWE-704) in the Loader component of Google Chrome prior to version 143.0.7499.41. This flaw allows potential heap corruption when processing a crafted HTML page, with Chromium assigning it a Medium security severity.
A remote attacker who has compromised the renderer process can exploit this vulnerability via a malicious HTML page. The CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates network-accessible exploitation with low complexity and no privileges required, but user interaction is needed, such as visiting a crafted webpage, potentially leading to high impacts on confidentiality, integrity, and availability.
Mitigation is available through the Google Chrome stable channel update for desktop, as announced at https://chromereleases.googleblog.com/2025/12/stable-channel-update-for-desktop.html. Additional technical details are provided in the Chromium issue tracker at https://issues.chromium.org/issues/457818670. Affected systems should be updated to Chrome 143.0.7499.41 or later.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2025-200305
Vulnerability Data
Bad cast in Loader in Google Chrome prior to 143.0.7499.41 allowed a remote attacker who had compromised the renderer process to potentially exploit heap corruption via a crafted HTML page. (Chromium security severity: Medium)
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation (static analysis, fuzzing, unit tests) directly finds incorrect type conversions or casts.
Requiring documented development standards and tools can mandate safe typing, casting rules, and compiler checks that stop the weakness from being introduced.
Security engineering principles can require type-safe design and casting practices that structurally avoid incorrect conversions.
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 prevent type-conversion flaws via coding standards, reviews, and testing.
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 can uncover type-conversion defects before release.
Secure development lifecycle includes type-safety reviews that reduce incorrect casts.
Application security requirements can mandate strong typing and safe casting rules.
Secure architecture principles discourage unsafe type conversions in design.
Secure coding standards directly forbid or detect incorrect type casts.