← All security news
SecurityPatchHIGH

Update Chrome: version 158 fixes 204 security flaws, six of them critical, and switches off XSLT for good on regular installs

· 1 min read

Chrome 158 reached the Stable channel on 17 November with 204 security fixes: 6 critical, 62 high. None is reported as exploited. The release also stops XSLT from working, which can break XML pages styled with it.

Google Chrome

Google promoted Chrome 158 to the Stable channel on 17 November 2026. The patched builds are 158.0.8127.36/.37 for Windows and macOS and 158.0.8127.36 for Linux, rolling out "over the coming days and weeks". The release carries 204 security fixes: 6 critical, 62 high, 82 medium and 54 low, according to SecurityWeek's count. Chrome 157 had 213.

The six critical flaws are all memory-safety bugs: use-after-free in WebView (CVE-2026-130963), GarbageCollection (CVE-2026-131008) and WebAudio (CVE-2026-130975), out-of-bounds writes in GPU (CVE-2026-131031) and ANGLE (CVE-2026-131054), and a buffer overflow in Media (CVE-2026-131060). Four were credited to Xinyang Ge of Anthropic, two of them "assisted by Claude", Cyber Security News and GBHackers report; the other two were found by Google. High-severity fixes include bugs in the V8 JavaScript engine, Autofill, extensions and downloads.

No exploitation is reported. SecurityWeek notes that "Google makes no mention of any of these vulnerabilities being exploited in the wild." Google may keep bug details private until most users have updated, so how far each flaw could be pushed is not public.

For web developers, Chrome 158 is also the release that switches off XSLT. Google's deprecation page says XSLT "stops functioning on Stable releases" from Chrome 158 for everyone outside the Origin Trial and the XSLTEnabled enterprise policy. Both the XSLTProcessor JavaScript class and the <?xml-stylesheet type="text/xsl" ...?> instruction are removed, so XML pages styled with XSLT, such as some RSS feeds, now show differently. Google cites the memory-safety history of the libxslt library and low use (about 0.02% of page loads). Both escape hatches stop working in Chrome 176, planned for 17 August 2027.

More news