Skip to content
CTI Academy Sponsor CTI Academy
HIGH · CVSS 8.8 CISA Known Exploited Vulnerability

CVE-2025-14174

Google Chromium Out of Bounds Memory Access Vulnerability

Google Chromium

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)

CVSS
8.8
HIGH
EPSS
55.3%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
12 Dec 2025
CWE-787, CWE-119

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 12 December 2025. US federal agencies were required to remediate it by 2 January 2026.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 55.3%, which is higher than 99% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Frequently asked questions

Is CVE-2025-14174 being exploited by ransomware groups?

No ransomware group in this database is currently recorded as exploiting CVE-2025-14174.

What does CVE-2025-14174 affect?

CVE-2025-14174 affects Google Chromium. 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)

How severe is CVE-2025-14174?

CVE-2025-14174 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 55.3%, higher than 99% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 2 January 2026.

How should organisations respond to CVE-2025-14174?

Apply the vendor patch for Google Chromium as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.