Live › vulnerability › CVE-2026-121167
Google Chrome before 157.0.8103.38 has an incorrect authorization flaw in its Permissions component. A remote attacker who already compromised the renderer process can use a crafted HTML page to bypass system access restrictions.
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 browser install of Chrome before 157.0.8103.38 is in scope, since the flaw sits in the browser's own permissions logic. The attacker must first compromise the renderer process, so this is a chained exploit rather than a standalone entry point. Managed fleets should confirm Chrome auto-update is working.
No product ranges from the sources yet.
chrome://settings/help shows the running version.157.0.8103.38.157.0.8103.38Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Incorrect authorization in Permissions in Google Chrome prior to 157.0.8103.38 allowed a remote attacker who had compromised the renderer process to bypass system access restrictions via a crafted HTML page. (Chromium security severity: Medium)
This page as .md · .json · in your agent: get_signal("CVE-2026-121167")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.