Live › vulnerability › CVE-2026-113193
Go to dashboardGoogle Chrome versions before 156.0.8078.47 have a memory corruption bug in the V8 JavaScript engine. A remote attacker who gets a user to open a crafted HTML page can potentially read memory inside the browser sandbox.
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.
Any machine with a Chrome build older than 156.0.8078.47 that browses untrusted web content is exposed, since the trigger is simply a crafted HTML page. Teams that run only managed, auto-updated Chrome fleets with recent builds can skip it, and the impact is limited to sandbox memory rather than full code execution as described.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| google chrome | vendor | < 156.0.8078.47 | 156.0.8078.47 |
google-chrome --version on Linux, and confirm it is at least 156.0.8078.47.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 V8 in Google Chrome prior to 156.0.8078.47 allowed a remote attacker to potentially read memory inside the sandbox via a crafted HTML page. (Chromium security severity: High)
This page as .md · .json · in your agent: get_signal("CVE-2026-113193")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.