CVE-2025-6558: Google Chromium ANGLE and GPU Improper Input Validation
Google Chromium · listed in the CISA catalog of actively exploited vulnerabilities since 2025-07-22.
- CVSS v3.1 (CVE record)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 11%
- higher than 95.9% of all CVEs
- Added to CISA KEV
- 2025-07-22
- US federal due date 2025-08-12
- Ubuntu priority
- high
CVE-2025-6558 explained
CVE-2025-6558 is an improper input validation flaw in the ANGLE and GPU components of Google Chrome before 138.0.7204.157. A remote attacker could use a crafted HTML page to potentially escape the browser sandbox. CISA lists it as a known exploited vulnerability, so patching should be treated as urgent.
Impact
An attacker needs no privileges, but a user must open a crafted HTML page delivered over the network. Successful exploitation could allow a sandbox escape, with high impact on confidentiality, integrity and availability. Any system where users browse untrusted web content with an affected Chromium or WebKit-based engine is exposed. CISA has added the flaw to its Known Exploited Vulnerabilities catalog.
Who is affected
Fixed: Debian 12 (bookworm) chromium 138.0.7204.157-1~deb12u1 and webkit2gtk 2.48.5-1~deb12u1. Debian 13 (trixie) webkit2gtk 2.48.5-1~deb13u1. Ubuntu 22.04 LTS webkit2gtk 2.48.5-0ubuntu0.22.04.1. Ubuntu 24.04 LTS webkit2gtk 2.48.5-0ubuntu0.24.04.1. Ubuntu 25.10 webkit2gtk 2.48.6-1ubuntu2. Debian 14 (forky, testing) webkit2gtk and wpewebkit 2.48.5-1. No fix: wpewebkit on Debian 12, Debian 13 and Ubuntu 22.04 LTS. qtwebkit-opensource-src on Ubuntu 22.04 LTS and 24.04 LTS. All listed packages on Ubuntu 16.04, 18.04 and 20.04 LTS.
Written with AI from the data on this page and checked against it automatically.
Official 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)
CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 138.0.7204.157
- 138.0.7204.157
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome |
|
|
Ubuntu and Debian releases
A server is vulnerable if it has a package built from the listed source package installed in a version lower than the fixed version for its release.
Ubuntu 25.10·webkit2gtk
end of life
Fixed: 2.48.6-1ubuntu2
Ubuntu 24.04 LTS·qtwebkit-opensource-src
Status: no fixed version published · Ubuntu tracker
Ubuntu 24.04 LTS·webkit2gtk
Fixed: 2.48.5-0ubuntu0.24.04.1
Ubuntu 22.04 LTS·qtwebkit-opensource-src
Status: no fixed version published · Ubuntu tracker
Ubuntu 22.04 LTS·webkit2gtk
Fixed: 2.48.5-0ubuntu0.22.04.1
Ubuntu 22.04 LTS·wpewebkit
Status: no fixed version published · Ubuntu tracker
Ubuntu 20.04 LTS·qtwebkit-opensource-src
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 20.04 LTS·webkit2gtk
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 20.04 LTS·wpewebkit
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·qtwebkit-opensource-src
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·qtwebkit-source
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·webkit2gtk
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 18.04 LTS·webkitgtk
standard support ended – later fixes only via Ubuntu Pro
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·qtwebkit-opensource-src
ESM ended
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·qtwebkit-source
ESM ended
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·webkit2gtk
ESM ended
Status: no fixed version published · Ubuntu tracker
Ubuntu 16.04 LTS·webkitgtk
ESM ended
Status: no fixed version published · Ubuntu tracker
Debian 14 (forky)·webkit2gtk
testing distribution
Fixed: 2.48.5-1
Debian 14 (forky)·wpewebkit
testing distribution
Fixed: 2.48.5-1
Debian 13 (trixie)·webkit2gtk
Fixed: 2.48.5-1~deb13u1
Debian 13 (trixie)·wpewebkit
Status: no fixed version published · Debian tracker
Debian 12 (bookworm)·chromium
Fixed: 138.0.7204.157-1~deb12u1
Debian 12 (bookworm)·webkit2gtk
Fixed: 2.48.5-1~deb12u1
Debian 12 (bookworm)·wpewebkit
Status: no fixed version published · Debian tracker
What to do
- Update
chromiumandwebkit2gtkto the fixed versions listed for your release. - Restart browsers and applications that use these engines so they load the patched libraries.
- On Ubuntu 18.04 LTS and 20.04 LTS, check Ubuntu Pro (ESM) for fixes, as standard support has ended.
- Upgrade Ubuntu 16.04 LTS and Ubuntu 25.10 systems to a supported release, since they are end of life.
- Track the distribution advisories for
wpewebkitandqtwebkit-opensource-srcfixes.
Until fixed wpewebkit or qtwebkit-opensource-src packages are published, limit their use for untrusted web content. Prefer a patched browser for general browsing, and remove applications built on unpatched engines where they are not needed. Do not wait for fixes on end-of-life releases such as Ubuntu 16.04 LTS; upgrade them to a supported release.
Written with AI from the data on this page and checked against it automatically.
Check and fix on a server
Run on each Ubuntu or Debian server. Replace chromium with the source package from the table above (this CVE affects 6 source packages).
1. Show installed packages built from the source package, with their versions
dpkg-query -W -f='${binary:Package} ${Version} ${source:Package}\n' | awk '$3=="chromium"'2. Compare each installed version with the fixed version for your release from the table (releases with a fixed version only)
I=INSTALLED_VERSION; F=FIXED_VERSION # replace both
dpkg --compare-versions "$I" lt "$F"; case $? in 0) echo vulnerable ;; 1) echo "fixed or newer" ;; *) echo "check the versions" ;; esac3. Install the fix
sudo apt update && sudo apt install --only-upgrade $(dpkg-query -W -f='${binary:Package} ${source:Package}\n' | awk '$2=="chromium"{print $1}')Services keep running the old code until they are restarted – restart the affected service or check with needrestart.
No fixed version yet on 2 releases
Ubuntu 20.04 LTS, Ubuntu 18.04 LTS: no fixed version of the affected packages yet, so every installed version there is affected. Until a fix is published:
- Follow the vendor's advisory for a mitigation or patch: chromereleases.googleblog.com/2025/07/stable-channel-upda…
- If the server does not need the package, remove it, or replace it with a maintained alternative.
- Restrict exposure: keep the affected service off the internet, limit access with a firewall or VPN, and turn off the vulnerable feature where you can.
This page updates automatically when Ubuntu or Debian publish a fix.
Ubuntu 16.04 LTS has reached end of life and no longer gets regular security fixes – upgrade to a supported release.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Weakness: CWE-20 Insufficient validation of untrusted input
Questions about CVE-2025-6558
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2025-6558 to its Known Exploited Vulnerabilities catalog on 2025-07-22, with a US federal due date of 2025-08-12. Whether it has been used in ransomware is unknown.
- Why are WebKit packages listed for a Chrome vulnerability?
- The distributions track
webkit2gtk,wpewebkitand Qt WebKit packages for this CVE as well aschromium. Update whichever of these packages are installed on your systems. - Does a user need to do anything for an attack to work?
- Yes. User interaction is required: the user must load a crafted HTML page. No privileges are needed and the attack can come over the network.
Written with AI from the data on this page and checked against it automatically.
References
Other advisories
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.