CVSS 3.1
9.6 criticalCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:HCVE-2026-120931 google chrome: Out-of-bounds Write
Critical (9.6) in google chrome. EPSS 0.4% estimated probability of exploitation activity in the next 30 days.
On this page
Out of bounds write in WebGL in Google Chrome on on Android prior to 156.0.8078.47 allowed a remote attacker to execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: Critical)
Severity
- EPSS
- 0.4% (unchanged from 0.4% a week ago) estimated probability of exploitation activity in the next 30 days; 37th 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-03. 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-787 Out-of-bounds Write
- Published
- Modified
- NVD analysis
- Analyzed
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-120931 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-120931?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-120931?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-120931 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
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:
[](https://cve.bz/cve/CVE-2026-120931)
HTML:
<a href="https://cve.bz/cve/CVE-2026-120931"><img src="https://cve.bz/cve/badge/CVE-2026-120931.svg" alt="CVE-2026-120931"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Google Chrome | from 156.0.8078.47 before 156.0.8078.47 |
Fix and patched versions
- Debian: fixed package versions per release
- Vendor advisory: https://chromereleases.googleblog.com/2026/10/stable-channel-update-for-desktop_02018666648.html
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12 | chromium | 156.0.8078.47-1~deb12u1 | DEBIAN-CVE-2026-120931 |
| Debian | 13 | chromium | 156.0.8078.47-1~deb13u1 | DEBIAN-CVE-2026-120931 |
| Debian | 14 | chromium | 156.0.8078.47-1 | DEBIAN-CVE-2026-120931 |
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 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-120931.