Vulnerabilities and exploitation

Chrome 158 fixes 204 security flaws, six of them critical

Google's latest desktop release patches six critical memory-safety bugs in Chrome for Windows, macOS and Linux. No exploitation has been reported.

By Junglewise News DeskPublished 4 min read
Google logo on glass office building facade surrounded by trees and grass
Asoundd, CC BY-SA 4.0 via Wikimedia Commons

Google has released Chrome 158 to the stable channel with fixes for 204 security vulnerabilities, six of them rated critical. The flaws affect the desktop browser on Windows, macOS and Linux,, and ACN lists the vulnerability types as arbitrary code execution, security restrictions bypass and information disclosure.

Italy's national cybersecurity agency, ACN, described the issues as allowing arbitrary code execution, bypass of security restrictions and information disclosure, and rated their systemic impact as "Alto (65.38)". The Canadian Centre for Cyber Security issued its own advisory, AV26-1171, on November 17, 2026. Google has not said that any of the 204 flaws have been used in attacks.

The fixed versions are Chrome 158.0.8127.36 or .37 for Windows and macOS, and 158.0.8127.36 for Linux. Anything older than that is in scope.

What to do now

  1. Update Chrome on every desktop you manage to 158.0.8127.36 or .37 on Windows and macOS, or 158.0.8127.36 on Linux. Check your current version under Chrome's About page, which also triggers the update check.
  2. Restart the browser after the update downloads. Chrome applies the patch on relaunch.
  3. If you manage Chrome centrally through group policy or a mobile device management tool, confirm that update rollout is not pinned to an older version or delayed by a staged rollout policy, and shorten the window if it is.
  4. Audit the long tail: kiosks, digital signage, shared machines, build agents and anything else where a browser quietly runs unattended. These rarely get relaunched and are easy to forget.
  5. Do not wait for proof of exploitation before acting. The Canadian Centre for Cyber Security encourages users and administrators to review the vendor link and apply the necessary updates as they become available, which is the sensible default for a browser release of this size.

Technical details

Chrome 158 patches 204 vulnerabilities: six critical, 62 high severity, 82 medium and 54 low. ACN published the breakdown in alert AL01/261118/CSIRT-ITA, citing Google's Chrome Releases stable channel desktop post from November 2026 as its reference, and listed 68 CVE identifiers covering the critical and high severity issues.

All six critical flaws are memory-safety defects. Three are use-after-free bugs, affecting the WebView, GarbageCollection and WebAudio components. Two are out-of-bounds write defects, one in the GPU component and one in ANGLE. The sixth is a buffer overflow in Media. Use-after-free means the browser keeps using a chunk of memory after releasing it, which an attacker can arrange to refill with data of their choosing. ANGLE is the graphics translation layer Chrome uses to talk to a system's GPU.

Across the whole release, use-after-free was the most common vulnerability type with 51 instances, followed by incorrect authorization (34), missing authorization (16), out-of-bounds write and read (15), uninitialized resource (14), information leak (11), user interface misrepresentation (10), improper input validation (9) and race condition (8).

Affected products are Google Chrome versions prior to 158.0.8127.36/.37 for Windows and macOS, and prior to 158.0.8127.36 for Linux. ACN recommends updating to the latest available version on all three platforms, in line with Google's own guidance.

Where the bugs came from

Google paid 11,000 dollars in rewards for five vulnerabilities reported by external researchers, and no reward at all for 163 of the 204 fixes, including every one of the six critical bugs. Bounty amounts for a further 36 flaws have not yet been decided.

Google itself found 145 of the unrewarded vulnerabilities, and researcher Xinyang Ge accounted for another 15. A patch count of 204 looks alarming at first glance, but 160 of the fixes came from Google's own staff and one researcher working with the project.

What is not yet known

Google did not indicate that any of the patched flaws had been attacked before the release, and no outlet in this reporting has claimed otherwise. The specific conditions required to trigger each critical flaw are not public. There is also no public indication of which of the 68 listed CVE identifiers map to which component beyond the six critical bugs described above.

No indicators of compromise have been published, which is consistent with a release driven by proactive discovery rather than incident response. SecurityWeek notes that users are nonetheless advised to update their browsers as soon as possible.

Share this article

On Junglewise Threat Intelligence

Related stories

Scan your domain free: see what attackers can see from outside, in about 30 seconds.

This article as Markdown. Atom feed.