Google has shipped an out-of-band Chrome update to close CVE-2025-13223, a high-severity type confusion vulnerability in the V8 JavaScript and WebAssembly engine. Google confirmed that an exploit for the bug exists in the wild, so this is the seventh actively exploited Chrome zero-day fixed in 2025.
What happened
The flaw was reported on 12 November 2025 by Clément Lecigne of Google’s Threat Analysis Group (TAG). TAG focuses largely on government-backed attackers and commercial surveillance vendors, so the bug was most likely used in targeted operations rather than mass exploitation. As usual, Google is withholding technical details and information about the attacks until most users have installed the fix.
The same release also patched CVE-2025-13224, a second V8 type confusion bug. Google’s AI-driven vulnerability research agent Big Sleep found that one in October, and there is no indication it has been exploited.
Technical details
- CVE: CVE-2025-13223, type confusion in V8, CVSS 8.8
- Fixed builds: 142.0.7444.175/.176 for Windows, 142.0.7444.176 for macOS, 142.0.7444.175 for Linux
- Attack vector: type confusion bugs in V8 can typically be triggered by a crafted web page and lead to memory corruption. In real attack chains they are often combined with a sandbox escape to fully compromise the device.
Of the earlier 2025 Chrome zero-days, the sixth, CVE-2025-10585 (patched in September), was also a V8 type confusion issue found by TAG.
Who is affected
Any Chrome installation older than 142.0.7444.175 is vulnerable. Other Chromium-based browsers, including Microsoft Edge, Brave, Opera and Vivaldi, inherit V8 fixes on their own release schedules and need to be updated once their vendors ship the patch.
Recommendations
- Update Chrome to 142.0.7444.175 or later and restart the browser. Pending updates are not applied until a relaunch.
- Use enterprise policy (for example Chrome Browser Cloud Management or GPO) to enforce a minimum version and flag outdated endpoints.
- Track vendor advisories for Chromium-based browsers and patch them as soon as builds with the V8 fix are available.
- High-risk users such as executives, journalists and diplomats should consider stricter browser hardening, including site isolation policies and limiting JavaScript on untrusted sites.