Should you update to Chrome 158.0.8127.36?

From Chrome updates, in the HARD wiki · Updated

Yes, this week. Chrome 158.0.8127.36 is a security update Google released on 17 Nov 2026 for Mac, Windows and Linux. It fixes 204 security flaws, 6 rated critical and 62 high by Google.[1] None of them is known to be used in attacks.

Hear about the next Chrome update the day it ships: get the alert below, or add the free HARD extension.

Should you update?

Yes, this week. Google rates 6 fixes critical, and attackers study each release to work out what it fixed. It is the newest Chrome release. The holes it closes became public the moment it shipped, so waiting a week to see if others hit problems is the wrong trade.

Is Chrome 158.0.8127.36 safe to install?

Yes. It’s Google’s own security release, and updates rarely go wrong; a backup makes it painless if one does. The one unsafe way to get it is from a link: Google never sends updates by email, text or pop-up, so install it only from Chrome’s own About page (chrome://settings/help).

What it fixes

Google lists 204 security flaws, 6 rated critical and 62 high by Google.[1]

The critical and high fixes68
FlawSeverityWhat Google calls it
CVE-2026-130963CriticalUse after free in WebView
CVE-2026-131031CriticalOut of bounds write in GPU
CVE-2026-131060CriticalBuffer overflow in Media
CVE-2026-131008CriticalUse after free in GarbageCollection
CVE-2026-131054CriticalOut of bounds write in ANGLE
CVE-2026-130975CriticalUse after free in WebAudio
CVE-2026-130910HighProtection mechanism failure in ANGLE
CVE-2026-130943HighUse after free in Chromecast
CVE-2026-130994HighUse after free in WebGL
CVE-2026-130909HighUse after free in Extensions
CVE-2026-131065HighUse after free in Autofill
CVE-2026-131100HighUse after free in Loader
CVE-2026-130979HighUse after free in Forms
CVE-2026-131079HighUse after free in Bindings
CVE-2026-130940HighImproper state validation in GPU
CVE-2026-130954HighIncorrect reference resolution in ANGLE
CVE-2026-130996HighOut of bounds write in ANGLE
CVE-2026-130970HighUninitialized resource in GPU
CVE-2026-131057HighOut of bounds read in ANGLE
CVE-2026-130945HighUse after free in VR
CVE-2026-131084HighUse after free in XML
CVE-2026-131090HighUse after free in Geometry
CVE-2026-130982HighIncorrect authorization in Omnibox
CVE-2026-131021HighUse after free in Accessibility
CVE-2026-131022HighUse after free in DOM
CVE-2026-131081HighIncorrect authorization in Media
CVE-2026-130961HighIncorrect authorization in Media
CVE-2026-130984HighIncorrect authorization in Canvas
CVE-2026-130946HighIncorrect authorization in PerformanceAPIs
CVE-2026-131045HighIncorrect authorization in PerformanceAPIs
and 38 more

How to update, and how long it takes

A minute or two. Chrome downloads it in the background, and relaunching reopens your tabs.

  1. Open Chrome’s About page.Type chrome://settings/help in the address bar, or open the ⋮ menu → Help → About Google Chrome. Chrome checks and downloads the update.
  2. Click Relaunch.Chrome reopens your tabs. Until you relaunch, the old, unfixed version keeps running.
  3. Do the same in every Chromium browser.Edge, Brave, Opera and Vivaldi are built on the same code and get the same fixes a few days later.

To check it worked: chrome://settings/help shows the version, and says “Chrome is up to date” when it is. It should say 158.0.8127.36 or later.

157.0.8103.78 vs 158.0.8127.36

Chrome 157.0.8103.78, released 11 Nov 2026, fixed 83 security flaws. Chrome 158.0.8127.36 fixes 204 security flaws and includes the fixes before it, so going straight to 158.0.8127.36 gets you both; you never need Chrome 157.0.8103.78 first. It is the newest release so far.

Also released 17 Nov 2026: Firefox 160.0.1. Every release and the latest version: Chrome updates; everything HARD tracks: Updates.

157.0.8103.78 and 158.0.8127.36 side by side
Release157.0.8103.78158.0.8127.36
Released
Security fixes83204
Critical, high5, 786, 62
Used in attacksNone knownNone known

Questions and references

Questions9

When was Chrome 158.0.8127.36 released?

Google released Chrome 158.0.8127.36 on 17 Nov 2026. It is the newest Chrome release so far.

What’s new in Chrome 158.0.8127.36?

Google released it as a security update that fixes 204 security flaws, 6 rated critical and 62 high by Google. None of them is known to be used in attacks. This page covers those fixes; Google’s own release notes have its full wording.

Should I update to Chrome 158.0.8127.36?

Yes, this week. Google rates 6 fixes critical, and attackers study each release to work out what it fixed.

Is Chrome 158.0.8127.36 safe to install?

Yes. It’s Google’s own security release, and updates rarely go wrong; a backup makes it painless if one does. The one unsafe way to get it is from a link: Google never sends updates by email, text or pop-up, so install it only from Chrome’s own About page (chrome://settings/help).

How long does the Chrome 158.0.8127.36 update take?

A minute or two. Chrome downloads it in the background, and relaunching reopens your tabs.

Is Chrome 158.0.8127.36 the latest Chrome release?

Yes. It is the latest security release for Chrome that we track.

Can I skip Chrome 158.0.8127.36?

You can, but you would stay open to 204 security flaws. Chrome 158.0.8127.36 includes the fixes from every earlier release, including Chrome 157.0.8103.78, so you never need to install them one by one.

What is the difference between Chrome 157.0.8103.78 and Chrome 158.0.8127.36?

Chrome 157.0.8103.78, released 11 Nov 2026, fixed 83 security flaws. Chrome 158.0.8127.36, released 17 Nov 2026, fixes 204 security flaws and includes the earlier fixes, so installing 158.0.8127.36 straight away covers both.

How do I check my installed Chrome version?

chrome://settings/help shows the version, and says “Chrome is up to date” when it is. It should say 158.0.8127.36 or later.

References1
  1. ^ Google. “Stable Channel Update for Desktop”, 17 Nov 2026.