Skip to content

Chrome 158 is rolling out with 204 security fixes, six of them Critical

Google's Chrome 158 stable release patches 204 security flaws, six rated Critical, on Windows, Mac and Linux. Here is what was fixed and how to update.

Chrome 158 Stable: 204 Security Fixes, 6 Rated Critical

Google promoted Chrome 158 to the stable channel on November 17, 2026, and the release carries 204 security fixes, six of them rated Critical. It is rolling out to Windows, Mac and Linux over the coming days and weeks, and none of those fixes protect you until Chrome has updated and relaunched.

What Chrome 158 fixes

Google’s Stable Channel Update lists 204 entries: 6 Critical, 62 High, 82 Medium and 54 Low. The build covers the changes between 157.0.8103.80 and 158.0.8127.36, so anyone moving up from Chrome 157 gets the whole batch at once.

The Critical list is CVE-2026-130963, a use-after-free in WebView; CVE-2026-131031, an out-of-bounds write in the GPU component; CVE-2026-131060, a buffer overflow in Media; CVE-2026-131008, a use-after-free in garbage collection; CVE-2026-131054, an out-of-bounds write in ANGLE; and CVE-2026-130975, a use-after-free in WebAudio. Google shows no bounty amount for any of the six.

Google credits two of those bugs to its own team. The other four go to researcher Xinyang Ge, with three listed under Anthropic and two of those marked as found with assistance from Claude. Anthropic has separately described its exploit research on Chrome and other platforms.

All six Critical entries are memory safety errors, the same class as the zero-day in last week’s Chrome 157 fix. Among the High entries, only one lists a bounty: $4,000 for CVE-2026-130910, a protection mechanism failure in ANGLE reported by Arni Hardarson of Neonix Security. Many other entries show the bounty as TBD.

GPU and ANGLE are the most frequent components among the High entries, with seven and six, ahead of four in Autofill. One of the Critical bugs also sits in each of the two graphics layers. Those two components handle how pages are drawn, which makes the update worth installing promptly on any machine that opens untrusted sites all day.

How to get the update today

Chrome updates itself, but the stable rollout is staged, so your copy may not have it yet. To check, open the Chrome menu, choose Help, then About Google Chrome. Chrome fetches the update there and asks for a relaunch to finish installing it.

Google first pushed 158.0.8127.36 and .37 to a small percentage of Windows users on November 12, with Mac to follow shortly, before Tuesday’s full promotion. If you were not in that early group, the same build is what reaches you now.

Windows and Mac builds are 158.0.8127.36 and .37, and Linux gets 158.0.8127.36. Google’s Android release post lists Chrome 158 as 158.0.8127.42, arriving on Google Play over the next few days. Android releases carry the same security fixes as the desktop build unless Google notes otherwise.

The stable post does not describe any new features. Google says separate Chrome and Chromium blog posts will cover what is new in 158. It also warns that bug details and links may stay restricted until most users have the fix, so the entries above are brief for now.

Leave a Reply

Your email address will not be published. Required fields are marked *