Google promoted Chrome 158 to the stable channel on November 17 with 204 security patches. Six of the fixes are critical, and no exploitation has been reported.
What Google Fixed in the Chrome 158 Release
The fixed builds for Windows, Mac and Linux desktop are 158.0.8127.36 and 158.0.8127.37. Versions before 158.0.8127.36 are affected.
Severity Breakdown of the 198 Reported Chrome Flaws
Google’s release post details 198 external and internal reports, split as 6 critical, 62 high, 78 medium and 52 low. GBookHub and PiunikaWeb report the 204-patch split as 6 critical, 62 high, 82 medium and 54 low, so figures differ between outlets; 204 is the headline count.
Highest-Scoring CVEs in the Chrome 158 Update
The notable vulnerabilities fall into two score bands:
- CVSS 9.6: CVE-2026-131031, CVE-2026-131054 and CVE-2026-130910
- CVSS 8.8: CVE-2026-131060, CVE-2026-131008 and CVE-2026-130975
CVE-2026-130963 is a use-after-free flaw that was unrated at the time of publication.
The Six Critical Chrome 158 CVEs by Component
The six critical CVEs by component are:
- CVE-2026-130963: use-after-free in WebView
- CVE-2026-131031: out-of-bounds write in GPU
- CVE-2026-131060: buffer overflow in Media
- CVE-2026-131008: use-after-free in GarbageCollection
- CVE-2026-131054: out-of-bounds write in ANGLE
- CVE-2026-130975: use-after-free in WebAudio
SecurityOnline scored the flaws up to 9.6. Other components patched include DevTools, Autofill, Extensions and V8 at various severities. Sources reviewed do not disclose bounty amounts or reporter names.
Chrome 158 Version Numbers for Android and Linux
Windows and macOS receive 158.0.8127.36 and .37, Linux receives 158.0.8127.36, and Android receives 158.0.8127.42 through Google Play. Rollout is gradual over days and weeks, and users can check manually under Settings > About Chrome.
Chrome 158 Begins Ending XSLT Support and Adds a Web App Install API
Chrome 158 begins ending support for XSLT, with the origin trial and policy exceptions fully disabled in Chrome 176. It also adds a direct web app install API.
Memory Flaws in the Browser Engine
The impact of the bugs listed is memory-related. Memory flaws in the browser engine can allow code execution or crashes. Use-after-free bugs such as CVE-2026-130963 are a common class of such flaws.
No exploitation has been confirmed for any of the Chrome 158 fixes. That separates this release from the browser’s recent zero-day activity.
How Chrome 158 Fits Google’s Recent Patch Cadence
Chrome has been updated repeatedly in the past week. A Chrome zero-day, CVE-2026-125350, was patched on November 10, and a Chrome 157 update fixed 83 flaws on November 12. Chrome 158 follows those releases, and it is a major version update that carries a much larger set of fixes.
The score bands and the component list do not map one-to-one. Of the three CVSS 9.6 entries, CVE-2026-131031 is an out-of-bounds write in GPU and CVE-2026-131054 is an out-of-bounds write in ANGLE, while the sources reviewed do not name a component for CVE-2026-130910. The 8.8 entries include a Media buffer overflow, a GarbageCollection use-after-free and a WebAudio use-after-free. Severity labels and CVSS scores differ between Google’s release post and third-party trackers, so administrators should rely on the fixed build numbers rather than any single score.
Update Guidance for Chrome Users
Users on Windows, Mac and Linux should update to 158.0.8127.36 or later. Chrome typically downloads updates in the background and applies them when the browser restarts, so keeping the browser open for long periods without restarting can leave a machine on a vulnerable build even after the update has been fetched.
The six critical flaws and the 62 high-severity ones give the update a significant security payload even without a known exploited bug. Administrators who manage Chrome across an organization should confirm that managed endpoints have moved to the fixed builds.
