Skip to main content
Menu
CVEs

CVE

Google Chrome out-of-sandbox memory read in GPU component

CVE-2026-131103EUVD-2026-127393GHSA-GW22-J6G2-9V2H

CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:N/A:N · Chrome rates this high

3.4LowCISA-ADP
Exploited
No known exploitation
Fix
Fixed in 158.0.8127.36
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 158.0.8127.36.

Published
Last modified
Reference
Last checked
30/100 · provisional
High (Chrome)
None on Exploit-DB, Metasploit or GitHub
On X
View the cve.now post
  • Exploitation: none
  • Automatable: no
  • Technical impact: partial

Summary

Google Chrome has a flaw in its GPU component where an uninitialized resource can be abused. A remote attacker who has already compromised the renderer process can read memory outside the sandbox by serving a crafted HTML page.

Written by a model from the sources below. Verify against them.

Original description

Uninitialized resource in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process to read memory outside the sandbox via a crafted HTML page. (Chromium security severity: High)

cve.now Index

30Pcve.now Index 30 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure7/25Reachable over the network without a login · Unknown: No advisory context yet
  • Reach20/20Affects Google Chrome (software on nearly every server, desktop or phone)
  • Severity3.4/10CVSS 3.4
  • No patch0/5No signal

What would change the score

  • Would score about 85 if added to CISA KEV
  • Would score about 80 if CISA's SSVC rates exploitation active
  • Would score about 45 if advisories confirm default setups are exposed

What to do

  • Upgrade to a fixed version: 158.0.8127.36.

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-131103 (Uninitialized resource in GPU in Google Chrome prior to 158.0.8127.36 allowed a remote attacker who had compromised the renderer process…), 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-131103 (entry last updated 2026-11-18):
Affected:
- Google Chrome: from 158.0.8127.36, fixed in 158.0.8127.36
Fixed versions: 158.0.8127.36.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-131103 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-131103 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_01699533288.html
- https://issues.chromium.org/issues/576954321
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-131103
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-131103"}.

Timeline

  1. CVE published
  2. First seen by cve.now1 day
  3. Posted on X by cve.now
  4. CISA SSVC assessment

    Exploitation: none · Automatable: no · Technical impact: partial

  5. Record last updated

Affected versions

  • Google Chrome

    From 158.0.8127.36 · fixed in 158.0.8127.36

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-131103

Is CVE-2026-131103 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-131103?

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

How do I fix CVE-2026-131103?

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

Why is it rated 3.4 Low?

CVSS 3.4 scores the worst case. Chrome rates it High.

More CVEs