CVE-2025-6558
Google Chromium ANGLE and GPU Improper Input Validation
- Published15 Jul 2025
- Added to CISA KEV22 Jul 2025
- Remediation due12 Aug 2025
Description
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 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HAffected products
Remediation
References
- https://chromereleases.googleblog.com/2025/07/stable-channel-update-for-desktop_15.html
- http://seclists.org/fulldisclosure/2025/Aug/0
- http://seclists.org/fulldisclosure/2025/Jul/30
- http://seclists.org/fulldisclosure/2025/Jul/32
- http://seclists.org/fulldisclosure/2025/Jul/35
- http://seclists.org/fulldisclosure/2025/Jul/37
- https://issues.chromium.org/issues/427162086
- https://lists.debian.org/debian-lts-announce/2025/08/msg00015.html
- https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2025-6558
- http://www.openwall.com/lists/oss-security/2025/08/02/1
and 1 more references
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2025-6558 being actively exploited?
Yes. CVE-2025-6558 is listed in the CISA Known Exploited Vulnerabilities (KEV) catalog, added 22 Jul 2025.
How severe is CVE-2025-6558?
CVE-2025-6558 has a CVSS 3.1 base score of 8.8, rated high. EPSS estimates a 9.46% probability of exploitation.
Which products are affected by CVE-2025-6558?
Affected products include Apple Safari, Google Chrome, Webkitgtk, Wpewebkit Wpe Webkit, Apple iPadOS, and 5 more.
How do I fix CVE-2025-6558?
Upgrade affected software to a fixed version, for example Apple Safari 18.6, Google Chrome 138.0.7204.157, Webkitgtk 2.48.5 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2025-6558 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. Because it is on the CISA KEV list, a risk for it never ranks below high, and the update that fixes it moves to the Emergency patch lane. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.