CVE-2025-6558

KEVGoogle Chromium ANGLE and GPU Improper Input Validation Vulnerability

Description

Google Chromium contains an improper input validation vulnerability in ANGLE and GPU. This vulnerability could allow a remote attacker to potentially perform a sandbox escape via a crafted HTML page. This vulnerability could affect multiple web browsers that utilize Chromium, including, but not limited to, Google Chrome, Microsoft Edge, and Opera.

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 3.1 vectorCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

PublishedJul 15, 2025

Last modifiedOct 1, 2026

Added to KEVJul 22, 2025

Remediation dueAug 12, 2025

References

chromereleases.googleblog.com/2025/07/stable-channel-update-for-desktop_15.htmlRelease Notes
issues.chromium.org/issues/427162086Issue TrackingPermissions Required
seclists.org/fulldisclosure/2025/Aug/0Third Party Advisory
seclists.org/fulldisclosure/2025/Jul/30Third Party Advisory
seclists.org/fulldisclosure/2025/Jul/32Third Party Advisory
seclists.org/fulldisclosure/2025/Jul/35Third Party Advisory
seclists.org/fulldisclosure/2025/Jul/37Third Party Advisory
openwall.com/lists/oss-security/2025/08/02/1Mailing List
openwall.com/lists/oss-security/2026/09/30/18Mailing List
lists.debian.org/debian-lts-announce/2025/08/msg00015.htmlMailing ListThird Party Advisory
cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-6558US Government Resource

0 recent articles mention this CVE

Risk assessment · High

Actively exploited. Patch immediately.

Exploitation: Confirmed in the wild (CISA KEV)
Federal remediation deadline: Overdue by 441 days
CVSS: 8.8 HIGH
EPSS (30-day exploit probability): 10.9% · top 4% of all CVEs
Weakness: CWE-20
Attack vector: Network, remotely reachable

Recommended actions

1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
2.Treat as emergency change: patch or isolate internet-facing instances first.
3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.