Chrome 158 patches 204 flaws, six rated critical

Google has released Chrome 158, a security update that fixes 204 flaws in its Chrome browser, including six vulnerabilities rated critical. The update reached the Stable channel for Windows, Mac and Linux on 17 November 2026, bringing desktop Chrome to versions 158.0.8127.36 and 158.0.8127.37 on Windows and Mac, and 158.0.8127.36 on Linux.
The same security fixes arrived on Android the same day in Chrome 158.0.8127.42, rolling out through Google Play. Google followed that on 18 November with Chrome 159.0.8154.18 for Android, released to a small percentage of users at first before a wider rollout.
Six critical memory-safety flaws
All six critical vulnerabilities are memory-safety errors, the class of bug that lets an attacker corrupt a program's memory and, in the worst case, run their own code. They span several parts of the browser: a use-after-free flaw in WebView, tracked as CVE-2026-130963; an out-of-bounds write in the graphics processor component, CVE-2026-131031; a buffer overflow in Media, CVE-2026-131060; a use-after-free flaw in garbage collection, CVE-2026-131008; an out-of-bounds write in ANGLE, the graphics layer Chrome uses to talk to device hardware, CVE-2026-131054; and a use-after-free flaw in WebAudio, CVE-2026-130975.
Graphics-related fixes feature prominently beyond the critical list too, with further high-severity flaws in the ANGLE and GPU components. Google has not confirmed that any of the six critical flaws is being exploited in the wild.
Two critical flaws found with AI help
Google credits Anthropic researcher Xinyang Ge, assisted by the Claude artificial intelligence system, with finding the critical GPU and Media flaws. Ge is also credited with finding several high-severity flaws in the same release, a notable example of AI-assisted security research feeding directly into a browser update used by hundreds of millions of people.
The researcher reports behind the release stretch back several months, which is normal for a large browser update: flaws are reported, fixed, tested and then shipped together once the release is ready.
Why updating promptly matters
The Chrome 158 release also carries the fix for an earlier exploited flaw, CVE-2026-125350, a use-after-free bug in Chrome's XML handling that Google patched on 9 November after confirming an exploit existed in the wild. That flaw was added to the US CISA catalogue of known exploited vulnerabilities on 10 November, with a remediation deadline of 24 November for federal civilian agencies.
Anyone still running an older Chrome build remains exposed to that exploited flaw as well as to the 204 issues fixed in Chrome 158. Chrome normally downloads updates in the background, but the fix only takes effect after the browser is relaunched, so users who leave the browser open for days can fall behind without realising it.
To update manually, open About Google Chrome from the Settings or Help menu. Chrome will check for updates and download any that are available, then prompt for a relaunch to apply them. The rollout reaches users over the coming days and weeks, so checking manually is the fastest way to make sure the new version is installed.