Live › vulnerability › CVE-2026-113340
Go to dashboardA memory corruption bug in ANGLE, the graphics translation layer in Google Chrome for Windows, can be triggered by a crafted HTML page. A remote attacker who gets a user to load that page could 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 Windows machine running Google Chrome older than is exposed, because the flaw is triggered simply by visiting a malicious page. Chrome on macOS and Linux, and Chromium-based browsers that have not shipped the fix, should be checked against their own advisories; the sources do not say whether they are affected. Teams that only use managed, auto-updated browsers on a current version can confirm the version and move on.
156.0.8078.47| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| google chrome | vendor | < 156.0.8078.47 | 156.0.8078.47 |
chrome://version in Chrome on Windows and compare the version with 156.0.8078.47156.0.8078.47156.0.8078.47 or laterEach row is the first time that source carried this signal. The analyst’s rows are its own findings.
Memory corruption in ANGLE in Google Chrome on on Windows 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: Medium)
This page as .md · .json · in your agent: get_signal("CVE-2026-113340")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.