cve.bz

CVE-2026-126846 google chrome: Use After Free

9.6 criticalEPSS 0.3%

Critical (9.6) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.

On this page
Use after free in Skia in Google Chrome on on Android prior to 157.0.8103.78 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)

Severity

CVSS 3.1

9.6 critical
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
EPSS
0.3% estimated probability of exploitation activity in the next 30 days; 25th percentile. Scored 2026-11-13. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-11-12. 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
Under analysis
Record from
the NVD, synced

Ask an AI about this CVE

Show the promptExplain CVE-2026-126846 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126846?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126846?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-126846 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-126846

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-126846](https://cve.bz/cve/badge/CVE-2026-126846.svg)](https://cve.bz/cve/CVE-2026-126846)

HTML:

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

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Google Chromefrom 157.0.8103.78 before 157.0.8103.78

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12, 13chromiumno fix listedDEBIAN-CVE-2026-126846
Debian14libskia, chromiumno fix listedDEBIAN-CVE-2026-126846

From the distributions' data via OSV.dev: the Debian Security Tracker. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian.

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.

ProductPackageStateAdvisory
Red Hat Enterprise Linux 10firefoxNot affected
Red Hat Enterprise Linux 6webkitgtkOut of support scope
Red Hat Enterprise Linux 7firefoxNot affected
Red Hat Enterprise Linux 7webkitgtk3Out of support scope
Red Hat Enterprise Linux 7webkitgtk4Affected
Red Hat Enterprise Linux 8firefoxNot affected
Red Hat Enterprise Linux 8webkit2gtk3Affected
Red Hat Enterprise Linux 9firefoxNot affected
Red Hat Enterprise Linux 9webkit2gtk3Affected

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-126846.

History

  1. Scored 9.6 critical

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

References

Check your stackJSON