CVE-2026-110920: Google Chrome memory corruption in V8

CVE-2026-110920 · Severity: high · CVSS 8.8 · Published 2026-10-15

Google Chrome's V8 JavaScript engine contains a memory corruption vulnerability that allows remote attackers to execute arbitrary code within the browser sandbox by crafting a malicious HTML page. This could lead to complete compromise of the affected user's browser session and data, though the sandbox limits further system access.

Technologies: Google Chrome. Vendors: Google.

Quick answers

Is CVE-2026-110920 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-110920 being exploited in the wild.
How severe is CVE-2026-110920?
High severity, with a CVSS score of 8.8, published 15 October 2026.
Which products and versions are affected?
Google Chrome prior to 155.0.8059.84.
Is there a fix for CVE-2026-110920?
Yes: fixed in Chrome 155.0.8059.84. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-110920 attacked?
It is attacked over the network, in a web application.
Am I affected by CVE-2026-110920?
Check whether you run Google Chrome at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

  • Fixed in: Chrome 155.0.8059.84

Technical details

Memory corruption in the V8 JavaScript engine allows remote code execution within Chrome's sandbox via a crafted HTML page. The vulnerability requires only network access and user interaction (visiting a malicious page); no authentication is needed. A successful exploit grants arbitrary code execution limited by the sandbox boundary.

Affected products

  • Google Chrome prior to 155.0.8059.84

Timeline

  • 2026-10-15: disclosed
  • 2026-10-15: patched

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.