Should you update to Chrome 150.0.7871.46?

From Chrome updates, in the HARD wiki · Updated
This article is about one Chrome release. For the latest version, see Chrome updates.

No: install Chrome 157.0.8103.38 instead. Chrome 150.0.7871.46 is a security update Google released on 30 Jun 2026 for Mac, Windows and Linux. It fixes 433 security flaws, 20 rated critical and 88 high by Google.[1] None of them is known to be used in attacks.

It has since been replaced by Chrome 150.0.7871.100, released 7 Jul 2026, which includes all of its fixes. If you’re on an older version, install that instead.

Should you update?

No: install Chrome 157.0.8103.38 instead. Chrome 157.0.8103.38 came out on 3 Nov 2026 and includes every fix in Chrome 150.0.7871.46, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.

Is Chrome 150.0.7871.46 still safe?

Not any more. The 28 updates since, up to Chrome 157.0.8103.38, fix 2,241 security flaws that Chrome 150.0.7871.46 doesn’t, and each became public the day its fix shipped. Installing it is safe: get it only from Chrome’s own About page (chrome://settings/help), never from a link in an email, text or pop-up.

What it fixes

Google lists 433 security flaws, 20 rated critical and 88 high by Google.[1] The 108 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-13774CriticalUse after free in Extensions
CVE-2026-13775CriticalUse after free in GPU
CVE-2026-14398CriticalUse after free in ANGLE
CVE-2026-13776CriticalType Confusion in Dawn
CVE-2026-13777CriticalInsufficient validation of untrusted input in iOSWeb
CVE-2026-13778CriticalUse after free in WebUSB
CVE-2026-13779CriticalUse after free in Chromoting
CVE-2026-13780CriticalInsufficient validation of untrusted input in ANGLE
CVE-2026-13781CriticalInsufficient validation of untrusted input in Skia
CVE-2026-14417CriticalUse after free in Dawn
CVE-2026-13782CriticalUse after free in Browser
CVE-2026-13783CriticalUse after free in Views
CVE-2026-13784CriticalUse after free in Views
CVE-2026-14419CriticalUse after free in Skia
CVE-2026-13785CriticalUse after free in Bluetooth
CVE-2026-14420CriticalOut of bounds read and write in Dawn
CVE-2026-13786CriticalUse after free in Ozone
CVE-2026-14427CriticalHeap buffer overflow in Skia
CVE-2026-13787CriticalUse after free in Chromoting
CVE-2026-13788CriticalUse after free in Fullscreen
CVE-2026-14382HighInsufficient validation of untrusted input in ANGLE
CVE-2026-13790HighSide-channel information leakage in Scroll
CVE-2026-14385HighHeap buffer overflow in ANGLE
CVE-2026-13791HighInsufficient validation of untrusted input in Downloads
CVE-2026-13792HighUse after free in Touchbar
CVE-2026-13793HighInsufficient policy enforcement in SVG
CVE-2026-14392HighOut of bounds write in Tint
CVE-2026-13794HighInsufficient validation of untrusted input in WebAppInstalls
CVE-2026-14422HighOut of bounds read and write in Tint
CVE-2026-13795HighInsufficient policy enforcement in Chrome for iOS
and 78 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 150.0.7871.100 or later.

149.0.7827.200 vs 150.0.7871.46

Chrome 149.0.7827.200, released 25 Jun 2026, fixed 3 security flaws. Chrome 150.0.7871.46 fixes 433 security flaws and includes the fixes before it, so going straight to 150.0.7871.46 gets you both.

References

  1. ^ Google. “Stable Channel Update for Desktop”, 30 Jun 2026.