Google patches Chrome V8 zero-day CVE-2026-11645, its fifth exploited Chrome flaw of 2026

Google has released an emergency Chrome update for CVE-2026-11645, a high-severity flaw in the V8 JavaScript engine. Google says an exploit for it exists in the wild. It is the fifth Chrome zero-day Google has patched in 2026.

Technical details

The bug is an out-of-bounds read and write in V8 that can corrupt the heap. A remote attacker can trigger it with a crafted HTML page. The result can range from leaking memory, which can help defeat ASLR, to running arbitrary code inside the renderer sandbox. An anonymous researcher reported the issue to Google about two weeks before the fix. In line with its usual practice, Google has not released technical details or information about the attacks. Analysts note that real-world exploit chains usually pair a renderer bug like this with a separate sandbox escape.

Fixed versions

  • Windows: 149.0.7827.102
  • macOS: 149.0.7827.103
  • Linux: 149.0.7827.102

The stable channel release fixed dozens of other security issues at the same time.

Context

Earlier Chrome zero-days in 2026 were CVE-2026-2441 (CSS, February), CVE-2026-3909 (Skia) and CVE-2026-3910 (V8) in March, and CVE-2026-5281 (Dawn/WebGPU) in April. V8 remains a favourite target because one memory-safety bug there gives a dependable first stage that can be delivered from any website.

Who is affected

All users of Chrome and other Chromium-based browsers (Edge, Brave, Opera, Vivaldi and others) until their vendors ship the V8 fix. Chromium is also embedded in Electron applications and in kiosk or VDI images, which often lag behind.

Recommendations

  • Force-update Chrome through enterprise policy and require a browser restart. Updates do not take effect until the browser relaunches.
  • Watch for and deploy matching fixes in Edge and other Chromium-based browsers.
  • Inventory Electron apps and embedded Chromium runtimes, and track their vendors’ update schedules.
  • For high-risk users, consider site isolation hardening and limiting JIT in untrusted contexts where policy allows.

Sources