Google fixes 52 Chrome flaws, including four critical bugs
Stable builds move to 156.0.8078.73/.74 on Windows and Mac and 156.0.8078.73 on Linux, with no exploitation stated.
68
Vulnerability1 · 1 read
CVE-2026-118320
Memory corruption in V8 JavaScript engine in Google Chrome
- CVSS 3.1
- 8.8 high
- EPSS
- —
- Published
- ·
- Modified
AI analysisSummaries by Vani AI
Memory corruption in V8, Chrome's JavaScript engine, lets a remote attacker potentially execute arbitrary code inside the browser sandbox. Exploitation requires no authentication: a victim merely visits a crafted HTML page. Successful exploitation yields code execution within the sandbox, which attackers typically chain with a sandbox escape for full compromise. Google rated the severity High.
What to do: Update Chrome to 156.0.8078.73 or later; Chrome's auto-update mechanism should apply the fix on relaunch. No workaround is documented.
| Product | Affected | Fixed in |
|---|---|---|
| Google Chrome | prior to 156.0.8078.73 | 156.0.8078.73 |
Estimated exposure
largeSmall share of Chrome's ~3 billion users unpatched — Chrome's dominant browser market share; most users auto-update, leaving only a small unpatched share reachable via malicious web pages.
Order-of-magnitude estimate by the model from install counts, market share and public scan data it knows; verify before quoting.
Description · NVD
Memory corruption in V8 in Google Chrome prior to 156.0.8078.73 allowed a remote attacker to potentially execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: High)