Skip to main content
cve.nowby Sazabi
← Vulnerabilities
CVE-2026-125349EUVD-2026-121391

Uninitialized resource in GPU in Google Chrome on on Android prior to 157.0.8103.50 allowed a remote attacker who had compromised the…

Exploited
No known exploitation
Fix
Fixed in 157.0.8103.50
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 157.0.8103.50.

Published
Last modified
24/100 · provisional
Medium (Chrome)
None on Exploit-DB, Metasploit or GitHub

Summary

Google Chrome for Android has a flaw in its GPU component, where an uninitialized resource can be read. A remote attacker who has already compromised the renderer process could use a crafted HTML page to read memory outside the sandbox.

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

Read the original description

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)

cve.now Index

24Pcve.now Index 24 of 100 · methodology v3 · provisional
  • Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
  • Exposure?/25Unknown. No advisory context yet
  • Reach20/20Affects Google Chrome (software on nearly every server, desktop or phone)
  • Severity4/10Rated medium by Chrome
  • No patch0/5No signal

What would change the score

  • Would score about 79 if added to CISA KEV
  • Would score about 74 if CISA's SSVC rates exploitation active
  • Would score about 46 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

  • Upgrade to a fixed version: 157.0.8103.50.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-125349 (Uninitialized resource in GPU in Google Chrome on on Android prior to 157.0.8103.50 allowed a remote attacker who had compromised the…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-125349 (entry last updated 2026-11-10):
Affected:
- Google Chrome: from 157.0.8103.50, fixed in 157.0.8103.50
Fixed versions: 157.0.8103.50.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-125349 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-125349 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html
- https://issues.chromium.org/issues/536663516
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-125349
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-125349.

Timeline

  1. CVE published
  2. First seen by cve.now

Affected versions

  • Google Chrome

    From 157.0.8103.50 · fixed in 157.0.8103.50

Evidence 4

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 2

  1. Link
  2. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-125349

Is CVE-2026-125349 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-125349?

Chrome: from 157.0.8103.50 before 157.0.8103.50.Source: cve.now feed data

How do I fix CVE-2026-125349?

Upgrade to a fixed version: 157.0.8103.50.Source: cve.now feed data

Sources

Related

More vulnerabilities