Live › vulnerability › CVE-2026-113093
Go to dashboardA memory corruption bug in Google Chrome's DisplayLocking feature lets a remote attacker run code inside the browser sandbox through a crafted HTML page. Exploitation requires a victim to load that page in an affected Chrome build.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 21:57 UTC. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|
| google chrome | vendor | < 156.0.8078.47 | 156.0.8078.47 |
Run chrome://version in Chrome and compare the version with 156.0.8078.47.
Update Google Chrome to 156.0.8078.47 or later.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Memory corruption in DisplayLocking in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)
This page as .md · .json · in your agent: get_signal("CVE-2026-113093")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.