Chrome 158 Delivers 204 Security Fixes Including Critical Code-Execution Bugs

Google released Chrome 158 on November 17, 2026, across Windows, macOS, and Linux, addressing a total of 204 security vulnerabilities—six of which are rated critical and can enable code execution. Users are receiving the updated versions—158.0.8127.36 for Linux, and either 158.0.8127.36 or .37 for Windows and macOS—as the roll-out progresses. The update should arrive on all devices over the coming days.

What are the biggest risks?

Half of the critical flaws stem from “use-after-free” bugs—errors where the browser uses memory it has already released. Three components are affected: WebView (CVE-2026-130963), garbage collection (CVE-2026-131008), and WebAudio (CVE-2026-130975). These bugs could crash processes, corrupt data, or in some cases allow code execution within certain browser components, though not necessarily at the full device level.

The other three critical bugs involve memory safety in graphics and media handling. One out-of-bounds write bug appears in the GPU component (CVE-2026-131031); another similar issue is found in ANGLE, Chrome’s graphics abstraction layer (CVE-2026-131054); and a buffer overflow affects the Media component (CVE-2026-131060). Such flaws risk memory corruption, which attackers could exploit to take control of processes.

Other notable fixes and the disclosure story

Beyond the critical vulnerabilities, the update addresses high-severity issues across Chrome’s JavaScript engine V8, Autofill, extensions, and downloads. Some of these involved missing or incorrect permission checks rather than memory errors.

Google independently disclosed the WebView and ANGLE problems. The other critical bugs were reported by researcher Xinyang Ge, with assistance from Anthropic’s Claude AI for the GPU and Media issues. A reward of $4,000 was awarded to Arni Hardarson of Neonix Security for identifying a high-severity ANGLE security issue (CVE-2026-130910).

The company hasn’t indicated whether any of these six critical bugs have been exploited in the wild, nor whether they might allow breakout from Chrome’s sandbox—an isolation mechanism limiting what browser processes can do. This update follows Chrome 157, which fixed 213 security flaws, and a separate patch earlier in November for a zero-day vulnerability known to be actively abused.

How to get the patch

Windows and macOS users can trigger the update via Chrome’s menu: navigate to Help → About Google Chrome, which prompts a check for updates. Once the download finishes, relaunching the browser completes the installation. Linux users should use their distribution’s package manager, then restart the browser to confirm their version has reached the patched build. IT and security teams are urged to verify the Chrome version deployed across their device fleet, especially where devices may have downloaded the update but not restarted.

Devices not showing Chrome 158 yet should appear in the update feed soon. Note that the browser restart is required to fully apply the fix.