Skip to content
[ SIGNAL VERIFIED ] INDEPENDENT CYBERCRIME JOURNALISMCLASSIFIED // THE UNDERGROUND HAS A NEWSROOM / RSS
.COM
Latest News
ALL NEWS
Newsroom

Chrome 158 Begins Stable Rollout With 204 Security Fixes

Google's Chrome 158 rollout includes 204 security fixes. Check the announced desktop and Android builds, complete the update and relaunch your browser.

Chrome 158 Begins Stable Rollout With 204 Security Fixes
PUBLISHED

Google promoted Chrome 158 to the stable channel on November 17, 2026. The official release announcement says the desktop update includes 204 security fixes and will reach Windows, macOS and Linux users over the following days and weeks.

Which builds were announced?

The announced Linux build is 158.0.8127.36. Windows and macOS receive 158.0.8127.36 or 158.0.8127.37. Google separately announced Android build 158.0.8127.42 and says corresponding Android releases normally include the desktop security fixes unless otherwise noted.

The release lists critical memory-safety issues in several browser components. Google keeps some bug details restricted while updates reach users or other affected projects prepare fixes. The announcement does not say that these newly listed issues are being exploited in attacks.

Finish the update, then verify it

Google’s update instructions explain that desktop users can open the browser menu, choose Help and then About Google Chrome to check the installed version and available update. Complete the relaunch when prompted. Mobile users should use their platform’s official app store.

For managed devices, follow the organization’s browser update policy and contact its administrator if an expected update remains unavailable. A rollout announcement and a completed installation are different milestones.

A practical check for organizations

IPCRIME analysis: Record the version running on representative endpoints after restart, then investigate devices that remain behind. Separate machines waiting for an approved rollout from machines where the update mechanism is failing. That makes it easier to assign an owner and resolve exceptions.

The release count helps describe the scope of maintenance, but it does not measure how many attacks an organization has experienced. Treat vulnerability announcements as a reason to complete deployment and verify coverage, while investigating any suspicious behavior on its own evidence.

Featured image: conceptual IPCRIME artwork, not a photograph or screenshot of this incident or product.

Editorial note

IPCRIME distinguishes public records and documented findings from allegations, analysis and commentary. Report corrections through our contact page.