Back to Newsroom

Threat intel5 min read

Chrome 158 fixes 204 security bugs, six of them critical

Google's Chrome 158 release patches 204 vulnerabilities. Three of the six critical bugs can lead to code running outside the browser sandbox, so update and relaunch now.

4Tify Team

Google moved Chrome 158 to the stable channel on 17 November 2026. The release carries 204 security fixes. Six are rated critical, 62 high, 82 medium and 54 low. None of them is marked as exploited, but three of the critical bugs can let a malicious web page run code outside Chrome's sandbox, so this one is worth installing quickly.

What happened

The desktop builds are 158.0.8127.36 for Linux and 158.0.8127.36 or .37 for Windows and macOS. Google is rolling them out over several days and weeks, so some machines will not see the update straight away. Chrome 158 for Android (158.0.8127.42) is arriving through Google Play over the next few days and carries the same security fixes.

All six critical issues are memory-safety bugs:

  • CVE-2026-130963: use-after-free in WebView (Chrome on Android)
  • CVE-2026-131031: out-of-bounds write in the GPU component
  • CVE-2026-131054: out-of-bounds write in ANGLE, the graphics layer Chrome uses to translate drawing calls
  • CVE-2026-131060: buffer overflow in Media
  • CVE-2026-131008: use-after-free in garbage collection
  • CVE-2026-130975: use-after-free in WebAudio

Google found the WebView and ANGLE bugs itself. One outside researcher found the other four, and Google notes that two of those were found with help from an AI model.

Why the sandbox detail matters

The release blog post itself doesn't describe impact. The CVE records Google filed the same day do. For the GPU, ANGLE and WebView bugs, they say a remote attacker could run arbitrary code outside the sandbox. In the GPU and ANGLE cases that takes nothing more than a crafted HTML page. The sandbox is the barrier that normally keeps a compromised tab away from the rest of the system, so escaping it is the serious part. For the Media, garbage-collection and WebAudio bugs, the records say code would run inside the sandbox.

CISA's scoring on the NVD entry for CVE-2026-131031 puts the GPU bug at CVSS 9.6, and ANGLE gets the same score. The three in-sandbox bugs score 8.8, and the WebView entry was still awaiting a score at the time of writing. CISA's assessment lists exploitation as "none", and none of these CVEs is in its Known Exploited Vulnerabilities catalog.

The high-severity list is long too. It covers a use-after-free in the V8 JavaScript engine, three use-after-free bugs in Mojo (Chrome's inter-process messaging), and authorization flaws in Autofill, Extensions and the Omnibox. A high-rated ANGLE flaw (CVE-2026-130910) earned its finder a $4,000 reward, and on Android it too may allow code to run outside the sandbox.

Chrome has already had one exploited zero-day this month. CVE-2026-125350, a use-after-free in the XML component, was fixed in Chrome 157.0.8103.50/.51 on 9 November and added to CISA's exploited list the next day. Chrome 158 includes that fix as well.

Who is affected

Anyone running Chrome older than 158.0.8127.36 on Windows, macOS or Linux, and Chrome on Android older than the 158 release. Other Chromium-based browsers such as Edge, Brave, Opera and Vivaldi share much of this code and will need their own updates. Check each vendor's release notes rather than assuming you're covered.

What to do now

  1. Open chrome://settings/help (or Help > About Google Chrome). Let Chrome download the update, then click Relaunch. The fix is only active after the restart.
  2. Go back to the same page and check that the version is 158.0.8127.36 or later.
  3. On Android, update Chrome from Google Play.
  4. On Linux installs managed by a package manager, pull the update there and restart the browser.
  5. Admins: don't treat "update downloaded" as "patched". Pull the running Chrome version across your endpoints, and chase machines that are waiting for a relaunch. A forced relaunch window in your Chrome policy helps.

The full CVE list and fixed builds are in Google's release notes.

Browsers are only one part of the picture. Our vulnerability scanning service reports outdated software versions across your hosts and flags the ones with known critical CVEs, so a missed browser restart doesn't sit unnoticed for weeks.

NEWSLETTER

The week’s news,
every Friday.

A short email with what we published that week. You can unsubscribe from any of them.

FRIDAY DIGEST · SAMPLE4TIFY NEWSROOM

This week in security

  • 01Attackers exploit critical Cisco Expressway flaw to gain root on clustered nodes
  • 02SonicWall ends Gen 6 firewall patches, even for critical flaws
  • 03WhatsApp fixes three flaws, one possibly used to back up scam messages

+ 6 MORE IN THIS ISSUE · UNSUBSCRIBE IN ONE CLICK

ONE OFFER

More than one product?
Get one offer.

Tell us what you need to protect and your budget, monthly or yearly. We combine the products into one offer and one contract, sized to that budget, and we stay with you after it is signed.

Ask for an offer Just tell us how many assets you have and what you want to spend.
Chrome 158: 204 security fixes, 6 critical bugs | 4Tify