Live › vulnerability › CVE-2026-121112
A flaw in the Permissions component of Google Chrome lets code that has already compromised the renderer process read memory out of bounds. An attacker who gets there via a crafted HTML page could potentially run code outside the browser sandbox.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-11-03 21:19 UTC. All times on this page are UTC.
Any desktop or mobile install of Google Chrome before 157.0.8103.38 is in scope, since the attack starts from a web page the browser loads. Chromium-based browsers that pick up the same fix are in scope too, and the sources do not say which ones. The attack needs a renderer compromise first, so the exposure is mainly for users who browse untrusted sites.
No product ranges from the sources yet.
chrome://version; affected builds are prior to 157.0.8103.38.157.0.8103.38 or later.Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Out of bounds read in Permissions in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process to potentially execute arbitrary code outside the sandbox via a crafted HTML page. (Chromium security severity: High)
This page as .md · .json · in your agent: get_signal("CVE-2026-121112")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.