Google fixes sixth exploited Chrome zero-day of 2026, V8 type confusion CVE-2026-85046

Google has released an emergency Chrome update for CVE-2026-85046, a high-severity type confusion vulnerability in the V8 JavaScript and WebAssembly engine. Google says an exploit for the flaw exists in the wild. This is the sixth actively exploited Chrome zero-day patched in 2026.

Technical details

  • The bug carries a CVSS score of 8.8. A crafted HTML page can trigger it and lead to code execution inside the browser sandbox; visiting the page is enough.
  • It was reported on 4 August 2026 by researcher Salvatore Gulizia, who received a $1,000 bounty. He described a compiler bug in V8 that gives an array the wrong element-kind map, a pattern that can be turned into read/write access on the JavaScript heap.
  • As usual, Google has withheld technical details and has not attributed the attacks while users update.

Fixed versions

  • Chrome Stable 152.0.7977.82/.83 for Windows and macOS, and 152.0.7977.82 for Linux. The update fixes 12 security issues in total.
  • Microsoft Edge Stable 152.0.4191.62 includes the fix. Because V8 is shared across Chromium, other Chromium-based browsers need their own updates.

CISA added the flaw to its Known Exploited Vulnerabilities catalogue and set a remediation deadline of 18 September 2026 for federal civilian agencies.

Context

Earlier exploited Chrome zero-days this year were CVE-2026-2441 (CSS), CVE-2026-3909 (Skia), CVE-2026-3910 (V8), CVE-2026-5281 (Dawn) and CVE-2026-11645 (V8). Renderer exploits like this one are usually paired with a sandbox escape or a kernel bug for full device compromise, and they are often used by commercial spyware vendors and state actors in targeted attacks.

Recommendations

  • Update Chrome to 152.0.7977.82 or later and relaunch the browser; check that enterprise auto-update policies are not blocking the rollout.
  • Update Edge and other Chromium-based browsers as soon as vendor builds are available.
  • Use browser management tooling to report out-of-date versions across the fleet.
  • High-risk users should consider stricter site isolation settings or V8 hardening features where available.

Sources