CVSS 3.1
3.4 lowCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:NCVE-2026-125349 google chrome: Use of Uninitialized Resource
Low (3.4) in google chrome. EPSS 0.3% estimated probability of exploitation activity in the next 30 days.
On this page
Uninitialized resource in GPU in Google Chrome on on Android prior to 157.0.8103.50 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: Medium)
Severity
- EPSS
- 0.3% estimated probability of exploitation activity in the next 30 days; 20th 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-10. 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-125349 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-125349?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-125349?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-125349 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-125349)
HTML:
<a href="https://cve.bz/cve/CVE-2026-125349"><img src="https://cve.bz/cve/badge/CVE-2026-125349.svg" alt="CVE-2026-125349"></a>
Affected
Versions
From the CNA's record in the CVE List.
| Product | Affected |
|---|---|
| Google Chrome | from 157.0.8103.50 before 157.0.8103.50 |
Fix and patched versions
- openSUSE: fixed package versions per release
- Vendor advisory: https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html
Linux distributions
| Distribution | Release | Package | Fixed in | Advisory |
|---|---|---|---|---|
| Debian | 12, 13, 14 | chromium | no fix listed | DEBIAN-CVE-2026-125349 |
| openSUSE | Tumbleweed | chromium | 157.0.8103.50-1.1 | openSUSE-SU-2026:12509-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.
History
- Scored 3.4 low
- Analyzed by the NVD
Changes since this site first stored the record. The same for every record: /api/public/changes.