cve.bz

CVE-2026-125350 Google Chromium: Use After Free

8.8 highKEVEPSS 1.0%

High (8.8) in Google Chromium. In CISA KEV since 2026-11-10. EPSS 1.0% estimated probability of exploitation activity in the next 30 days.

On this page
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)

Severity

CVSS 3.1

8.8 high
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS
1.0% estimated probability of exploitation activity in the next 30 days; 62nd percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-11-10, due 2026-11-24
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-11-09. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-416 Use After Free
Published
Modified
Assigned by
Chrome (CNA)
NVD analysis
Analyzed
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-125350 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125350?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125350?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-125350 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-125350

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-125350](https://cve.bz/cve/badge/CVE-2026-125350.svg)](https://cve.bz/cve/CVE-2026-125350)

HTML:

<a href="https://cve.bz/cve/CVE-2026-125350"><img src="https://cve.bz/cve/badge/CVE-2026-125350.svg" alt="CVE-2026-125350"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 157.0.8103.50 before 157.0.8103.50

Fix and patched versions

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13, 14chromiumno fix listedDEBIAN-CVE-2026-125350
openSUSETumbleweedchromium157.0.8103.50-1.1openSUSE-SU-2026:12509-1
Alpinev3.21libxslt1.1.42-r3ALPINE-CVE-2026-125350
Alpinev3.22, v3.23, v3.24libxslt1.1.43-r4ALPINE-CVE-2026-125350
Azure Linux3libxsltno fix listedAZL-113561
Alpaquita25, streamlibxslt1.1.43-r2BELL-CVE-2026-125350
BellSoft Hardened Containers25, streamlibxslt1.1.43-r2BELL-CVE-2026-125350

From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0; the Alpine secdb, CC BY-SA 4.0; Microsoft's Azure Linux vulnerability data, MIT; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · openSUSE · Alpine · Alpaquita · BellSoft Hardened Containers.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates the severity of this flaw as determined by the Google Chrome Security Advisory.

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-125350.

GitHub PoC (unverified)

Repositories on GitHub named after this CVE. Nobody has checked them and they are not scanned: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

History

  1. Listed in CISA KEV
  2. Scored 8.8 high
  3. Analyzed by the NVD

Changes since this site first stored the record. The same for every record: /api/public/changes.

References

Check your stackJSON