Cyber Resilience

CVE-2025-14174

Memory Safety in Google Chrome 143.0.7499.41 – 143.0.7499.110

CISA KEVActive ExploitationEUVD ExploitedMemory Safety
Published
12 December 2025
Modified
15 December 2025
KEV Added
12 December 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.23 98th percentile
Risk Priority 90 floored blend · peak EPSS

Summary

CVE-2025-14174 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 2% of CVEs by exploit likelihood; CISA has added it to the Known Exploited Vulnerabilities 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-14174 is an out-of-bounds memory access vulnerability in the ANGLE graphics component of Google Chrome on Mac, affecting versions prior to 143.0.7499.110. A remote attacker can trigger this issue via a crafted HTML page, leading to improper memory access. It maps to CWE-787 (Out-of-bounds Write) and CWE-119 (Buffer Overflow), with 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 Chromium security severity rated as High.

The vulnerability can be exploited by a remote attacker with no privileges required, though it depends on user interaction such as visiting a malicious site. Exploitation enables out-of-bounds memory access, potentially resulting in high-impact compromise of confidentiality, integrity, and availability without scope changes.

Mitigation is available through patching: Google Chrome users on Mac should update to version 143.0.7499.110 or later, as announced in the stable channel update for desktop on the Chrome Releases blog. Related details appear in the Chromium issue tracker at issues.chromium.org/issues/466192044 and Microsoft Edge security release notes. The vulnerability is also listed in the CISA Known Exploited Vulnerabilities Catalog.

This issue has seen real-world exploitation, as indicated by its inclusion in the CISA catalog.

EU & UK References

Vulnerability Data

Out of bounds memory access in ANGLE in Google Chrome on Mac prior to 143.0.7499.110 allowed a remote attacker to perform out of bounds memory access via a crafted HTML page. (Chromium security severity: High)

CWE(s)
CWE-787CWE-119
KEV Date Added
12 December 2025

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 Macosboth on KEV
CVE-2026-3910Same product: Apple Macosboth on KEV
CVE-2026-20700Same product: Apple Ipadosboth on KEV
CVE-2025-31200Same product: Apple Ipadosboth on KEV
CVE-2022-22675Same product: Apple Ipadosboth on KEV
CVE-2021-30665Same product: Apple Ipadosboth on KEV
CVE-2021-30883Same product: Apple Ipadosboth on KEV
CVE-2012-0754Same product: Linux Linux Kernelboth on KEV
CVE-2022-32894Same product: Apple Ipadosboth on KEV
CVE-2023-32435Same product: Apple Ipadosboth on KEV

Affected Assets

google
chrome
143.0.7499.41 — 143.0.7499.110 · 143.0.7499.40 — 143.0.7499.109 · ≤ 143.0.7499.40
apple
safari
≤ 26.2
apple
ipados
≤ 18.7.3 · 26.0 — 26.2
apple
iphone os
≤ 18.7.3 · 26.0 — 26.2
apple
macos
≤ 26.2
apple
tvos
≤ 26.2
apple
visionos
≤ 26.2
apple
watchos
≤ 26.2
microsoft
edge chromium
≤ 143.0.3650.80

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)
  • V17.3.2

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.

SA-8 Security and Privacy Engineering Principles partial match

Secure engineering principles require memory-safe design and coding that structurally avoids buffer-boundary violations.

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.

ID.RA-08 partial match
prevents

Receiving and triaging vulnerability disclosures commonly includes buffer-related reports.

PR.AT-02 partial match
prevents

Developer training on secure coding reduces introduction of memory-buffer errors.

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