CVE-2026-125350: Google Chromium Use-After-Free
Google Chromium · listed in the CISA catalog of actively exploited vulnerabilities since 2026-11-10.
- CVSS v3.1 (Debian)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 1.9%
- higher than 80% of all CVEs
- Added to CISA KEV
- 2026-11-10
- US federal due date 2026-11-24
- Ubuntu priority
- –
CVE-2026-125350 explained
CVE-2026-125350 is a use-after-free flaw in the XML component of Google Chromium, fixed upstream in Google Chrome 157.0.8103.50. A crafted HTML page can let a remote attacker run arbitrary code inside the browser sandbox. CISA lists it as a known exploited vulnerability, so it should be treated as a priority.
Impact
A remote attacker who gets a user to open a crafted HTML page can execute arbitrary code inside the Chromium sandbox. No privileges are needed and attack complexity is low, but the user must interact, for example by visiting a malicious page. Confidentiality, integrity and availability impact are all rated high. The code runs within the sandbox and the scope is unchanged. CISA reports active exploitation. Known ransomware use is unknown.
Who is affected
The Debian source package chromium is affected in Debian 12 (bookworm) and Debian 13 (trixie), both supported stable releases. It is also affected in Debian 14 (forky), which is the Debian testing distribution, not a stable release. No fixed version has been published for any of these releases. Upstream, the issue is fixed in Google Chrome 157.0.8103.50. No Ubuntu releases are listed in the facts.
Written with AI from the data on this page and checked against it automatically.
Official description
Use after free in XML in Google Chrome prior to 157.0.8103.50 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
CISA required action: Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk guidance and CISA’s “Forensics Triage Requirements”. Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.
CISA notes
Upstream versions (CVE record)
From the CVE record published by the vendor or CVE numbering authority.
- Google ChromeAffectedFixed in
- < 157.0.8103.50
- 157.0.8103.50
| 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.
Debian 14 (forky)·chromium
testing distribution
Status: no fixed version published · Debian tracker
Debian 13 (trixie)·chromium
Status: no fixed version published · Debian tracker
Debian 12 (bookworm)·chromium
Status: no fixed version published · Debian tracker
What to do
- Identify all systems with the Debian
chromiumpackage installed, including desktops and kiosk machines. - Monitor the Debian security tracker and advisories for a fixed
chromiumpackage for bookworm, trixie and forky. - Install the fixed
chromiumpackage as soon as it is published. - Fully close and restart all Chromium instances after updating, because running browsers keep using the old code.
- Follow CISA's required action for this known exploited vulnerability where it applies to your organization.
Until Debian publishes a fixed chromium package, reduce exposure. Limit Chromium use on sensitive systems and avoid browsing untrusted sites. Consider restricting web access through filtering or proxies. If the risk is unacceptable, stop using Chromium on affected hosts until an update is available, in line with CISA's guidance to discontinue use if mitigations are unavailable.
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.
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"'No fixed version available
No Ubuntu or Debian release has published a fixed version of chromium yet, so every installed version is affected. Until a fix is published:
- Follow the vendor's advisory for a mitigation or patch: chromereleases.googleblog.com/2026/11/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.
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-416 Use after free
Questions about CVE-2026-125350
- Is this vulnerability being exploited?
- Yes. CISA added CVE-2026-125350 to its Known Exploited Vulnerabilities catalog on 2026-11-10, with a US federal due date of 2026-11-24. Whether it is used in ransomware campaigns is unknown.
- Can an attacker take over the whole system?
- The description says code execution happens inside the Chromium sandbox. Exploitation requires a user to open a crafted HTML page. The facts do not describe a sandbox escape.
- Is a fixed Debian package available?
- Not yet. No fixed
chromiumversion has been published for Debian 12 (bookworm), Debian 13 (trixie) or Debian 14 (forky). Upstream fixed the issue in Google Chrome157.0.8103.50.
Written with AI from the data on this page and checked against it automatically.
References
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.