Live › vulnerability › CVE-2026-121063
Google Chrome's CacheStorage component has an incorrect authorization check that lets a remote attacker who already controls the renderer process bypass site isolation via a crafted HTML page. Chromium rates it Medium severity.
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.
Anyone running Google Chrome before 157.0.8103.38 is exposed, since the flaw is in the browser itself. Exploitation requires a compromised renderer process first, so the risk is mainly a chained attack that starts with a malicious page.
No product ranges from the sources yet.
157.0.8103.38157.0.8103.38 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Incorrect authorization in CacheStorage in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process to bypass site isolation via a crafted HTML page. (Chromium security severity: Medium)
This page as .md · .json · in your agent: get_signal("CVE-2026-121063")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.