Chrome 158 Fixes 204 Vulnerabilities, Including Critical Code Execution Flaws
Google releases Chrome 158 with 204 security fixes, including 6 critical code execution flaws.
Google rolled out Chrome 158 on November 17, 2026, addressing 204 vulnerabilities across Windows, macOS, and Linux. Six critical flaws—three use-after-free bugs in WebView, garbage collection, and WebAudio, plus three memory errors in GPU, ANGLE, and Media components—could enable code execution. The patched builds are 158.0.8127.36 for Linux and 158.0.8127.36/37 for Windows/macOS; Google did not indicate active exploitation of these flaws.
AI summary of the linked source. Not reviewed by an editor. How this works
Run Google?
Get an email when a new story names Google, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
The lesson from this incident
Full lessonGoogle's Chrome 158 release addressed 204 vulnerabilities, six of them critical, spanning memory safety issues such as use-after-free bugs and memory errors in core browser components like WebView, GPU, and WebAudio. Memory safety flaws of this type are among the most dangerous classes of vulnerability because they can allow attackers to execute arbitrary code within the context of the browser, potentially compromising the underlying system. While Google reported no active exploitation, unpatched browsers in enterprise environments represent an open attack surface that adversaries routinely probe. Organizations that lack enforced, timely browser update policies are exposed for every day a critical patch goes unapplied.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Device management (MDM and UEM)
Every company laptop and phone is known, encrypted, locked down and up to date.
Indicators of Compromise
Addresses and file hashes are copied from the publisher's page by pattern matching. Names are picked by AI. On stories from before 17 November 2026, some addresses and hashes were picked by AI too. Not reviewed by an editor. How this works
- cve: CVE-2026-131060
- cve: CVE-2026-131031
- cve: CVE-2026-130975
- cve: CVE-2026-130910
- cve: CVE-2026-131054
- cve: CVE-2026-130963
- cve: CVE-2026-131008