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

CVE-2025-6558

Google Chromium ANGLE and GPU Improper Input Validation Vulnerability

Google Chromium

Insufficient validation of untrusted input in ANGLE and GPU in Google Chrome prior to 138.0.7204.157 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

CVSS
8.8
HIGH
EPSS
10.9%
30-day exploitation
Ransomware groups
0
recorded exploiting
Published
15 Jul 2025
CWE-20

Exploitation status

CISA Known Exploited Vulnerabilities

Listed by CISA on 22 July 2025. US federal agencies were required to remediate it by 12 August 2025.

EPSS — exploitation probability

FIRST puts the probability of exploitation activity in the next 30 days at 10.9%, which is higher than 95.9% 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-6558 being exploited by ransomware groups?

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

What does CVE-2025-6558 affect?

CVE-2025-6558 affects Google Chromium. Insufficient validation of untrusted input in ANGLE and GPU in Google Chrome prior to 138.0.7204.157 allowed a remote attacker to potentially perform a sandbox escape via a crafted HTML page. (Chromium security severity: High)

How severe is CVE-2025-6558?

CVE-2025-6558 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 10.9%, higher than 95.9% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 12 August 2025.

How should organisations respond to CVE-2025-6558?

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.