Live › vulnerability › CVE-2026-113051
Go to dashboardA memory corruption bug in Chrome's CSS handling lets a remote attacker who lures a user to a crafted HTML page read memory inside the browser sandbox. The sources rate it Medium and do not report exploitation in the wild.
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 user running Google Chrome before who browses to untrusted pages is exposed, since the trigger is a crafted HTML page. Teams with managed browsers should confirm the fleet version. Users on other Chromium-based browsers should check that browser's own release, since the sources only name Chrome.
156.0.8078.47| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| google chrome | vendor | < 156.0.8078.47 | 156.0.8078.47 |
google-chrome --version and compare against 156.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 CSS 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: Medium)
This page as .md · .json · in your agent: get_signal("CVE-2026-113051")
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.