CVSS 3.1
4.7 mediumCVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:N/A:NCVE-2026-126870 google chrome: Use of Uninitialized Resource
Medium (4.7) in google chrome. EPSS 0.2% estimated probability of exploitation activity in the next 30 days.
On this page
Uninitialized resource in ANGLE in Google Chrome prior to 157.0.8103.78 allowed a remote attacker to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High)
Severity
- EPSS
- 0.2% estimated probability of exploitation activity in the next 30 days; 15th 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: partial, 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-908 Use of Uninitialized Resource
- Published
- Modified
- Assigned by
- Chrome (CNA)
- NVD analysis
- Analyzed
- Record from
- the NVD, synced
Ask an AI about this CVE
Show the prompt
Explain CVE-2026-126870 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-126870?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-126870?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-126870 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-126870)
HTML:
<a href="https://cve.bz/cve/CVE-2026-126870"><img src="https://cve.bz/cve/badge/CVE-2026-126870.svg" alt="CVE-2026-126870"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Google Chrome | from 157.0.8103.78 before 157.0.8103.78 |
Fix and patched versions
- Vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_01744469280.html
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | chromium | no fix listed | DEBIAN-CVE-2026-126870 |
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.
This vulnerability is rated as Important severity because successful exploitation allows an attacker to escape sandbox boundaries and expose sensitive process memory, elevating the confidentiality risk beyond typical browser-level isolation. In Red Hat Enterprise Linux environments, chromium-browser is primarily used in graphical workstation deployments where processing web content is user-initiated. Exploitation requires user interaction, specifically convincing a user to navigate to a malicious web page, preventing automated or unassisted remote attacks.
Mitigation for this issue is either not available or the currently available options do not meet the Red Hat Product Security criteria comprising ease of use and deployment, applicability to widespread installation base, or stability.
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-126870.
History
- Scored 4.7 medium
- Analyzed by the NVD
Changes since this site first stored the record. The same for every record: /api/public/changes.