Chrome 158 fixes 204 security bugs, six rated critical

Published

Google has promoted Chrome 158 to the stable channel for Windows, Mac and Linux with 204 security fixes, six of them rated Critical, according to the Chrome team's November 17 release notes. The fixed builds are 158.0.8127.36 on Linux and 158.0.8127.36/.37 on Windows and Mac, rolling out over the coming days and weeks. Hong Kong's HKCERT has issued a bulletin urging users to update.

Google's release notes do not say that any of the bugs is being exploited, unlike the Chrome zero-day fixed earlier this month. Google rates each bug by its own severity scale and publishes no CVSS scores. Bug details stay restricted until most users have the fix.

Six critical memory bugs top the list

By Google's count the release carries 6 Critical, 62 High, 82 Medium and 54 Low fixes. The critical ones, as Google labels them:

Google has not described how any of these could be triggered or what an attacker would gain, so the component and bug class are the full extent of what is public.

AI-assisted research shows up in the credits

Most of the fixes, 145 of them, are credited to Google itself. Among outside reporters, Xinyang Ge is credited on 15 bugs, four of the six critical ones among them, and seven of those entries note the research was assisted by Claude, Anthropic's AI model. Three further High-severity authorization bugs, two in Media and one in PerformanceAPIs, are credited jointly to Anthropic and Ada Logics, and one Low-severity bug to Anthropic's Vlad Stolyarov, also assisted by Claude. The size of the release continues a run of very large Chrome updates, after Chrome 157 fixed 213 security bugs earlier this month.

Update to Chrome 158.0.8127.36 or later

Chrome updates itself, but the new version only takes effect after a restart. Open the browser's About Chrome page to trigger the update and relaunch. Administrators managing fleets should push 158.0.8127.36 (Linux) or 158.0.8127.36/.37 (Windows and Mac) or later. Other Chromium-based browsers typically ship the same fixes on their own schedules, so check those vendors as well.

None of these 204 bugs is known to be under attack, which makes this the cheap moment to patch: before anyone reverse engineers the fixes.

This briefing is provided by IntelFusions for informational and defensive purposes only. It is based on sources assessed to be reliable at the time of writing, and analytic judgments carry the confidence levels indicated. Indicators of compromise are defanged; re-arm them only in controlled environments. IntelFusions is not affiliated with the organizations named and makes no warranty as to completeness or accuracy.

Read the full analysis on IntelFusions