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-121037 google chrome: Out-of-bounds Write
Critical (9.6) in google chrome. EPSS 0.5% estimated probability of exploitation activity in the next 30 days.
On this page
Out of bounds write in ANGLE in Google Chrome on on Windows prior to 157.0.8103.38 allowed a remote attacker to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Severity
- EPSS
- 0.5% (unchanged from 0.5% a week ago) estimated probability of exploitation activity in the next 30 days; 40th 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-04. 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-121037 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-121037?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-121037?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-121037 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-121037)
HTML:
<a href="https://cve.bz/cve/CVE-2026-121037"><img src="https://cve.bz/cve/badge/CVE-2026-121037.svg" alt="CVE-2026-121037"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Google Chrome | from 157.0.8103.38 before 157.0.8103.38 |
Fix and patched versions
- openSUSE: fixed package versions per release
- Vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | chromium | no fix listed | DEBIAN-CVE-2026-121037 |
| openSUSE | Tumbleweed | chromium | 157.0.8103.38-1.1 | openSUSE-SU-2026:12426-1 |
From the distributions' data via OSV.dev: the Debian Security Tracker; SUSE security data, CC BY 4.0. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · openSUSE.
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.
--- CME Mitigation Guidance (2026-11-04) ---
Disclaimer: The following mitigation solutions are provided as a courtesy, pending the application of an official patch. This content was generated utilizing AI tools in conjunction with data from https://cmetaxonomy.org. Customers are advised to independently evaluate and test these temporary mitigations within their own infrastructure.
The highest-value action is to prevent out-of-bounds memory writes within the ANGLE graphics abstraction layer during web rendering: upgrade to Google Chrome 157.0.8103.38 (or the fixed Chromium builds), which corrects memory bounds validation within the ANGLE graphics abstraction layer, closing crafted HTML page rendering graphics via ANGLE. Until patched, this is only a concern on Chromium installations on Windows — Linux and macOS deployments are unaffected — so restrict user browsing to trusted internal destinations and block navigation to untrusted or unknown external web pages. As a compensating measure, enable address space layout randomization to impede reliable memory address calculation, enforce control flow integrity to validate indirect call targets against hijacked function pointers in ANGLE, enable arbitrary code guard to prevent allocating or converting writable memory into executable code, deploy Windows Defender Application Control in enforced mode to block unauthorized binaries dropped after sandbox escape, deploy endpoint detection and response to monitor and alert on anomalous post-escape process behavior, and enforce non-executable memory protections via the NX/XD bit to block shellcode execution in corrupted data structures. These controls limit blast radius and contain exploitation, but they do not fix the underlying out-of-bounds write defect — apply the upstream patch to fully remediate.
Highest-impact CME: CME-101 ASLR (Address Space Layout Randomization) (medium)
| Product | Package | State | Advisory |
|---|---|---|---|
| Red Hat Enterprise Linux 10 | firefox | Not affected | |
| Red Hat Enterprise Linux 10 | thunderbird | Not affected | |
| Red Hat Enterprise Linux 6 | webkitgtk | Out of support scope | |
| Red Hat Enterprise Linux 7 | firefox | Not affected | |
| Red Hat Enterprise Linux 7 | webkitgtk3 | Out of support scope | |
| Red Hat Enterprise Linux 7 | webkitgtk4 | Affected | |
| Red Hat Enterprise Linux 8 | firefox | Not affected | |
| Red Hat Enterprise Linux 8 | mozjs60 | Not affected | |
| Red Hat Enterprise Linux 8 | thunderbird | Not affected | |
| Red Hat Enterprise Linux 8 | webkit2gtk3 | Affected | |
| Red Hat Enterprise Linux 9 | firefox | Not affected | |
| Red Hat Enterprise Linux 9 | thunderbird | Not affected | |
| Red Hat Enterprise Linux 9 | webkit2gtk3 | Affected |
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-121037.