Should you update to Chrome 149.0.7827.155?

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 149.0.7827.155 is a security update Google released on 16 Jun 2026 for Mac, Windows and Linux. It fixes 33 security flaws, 7 rated critical and 26 high by Google.[1] None of them is known to be used in attacks.

It has since been replaced by Chrome 149.0.7827.196, released 23 Jun 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 149.0.7827.155, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.

Is Chrome 149.0.7827.155 still safe?

Not any more. The 31 updates since, up to Chrome 157.0.8103.38, fix 2,695 security flaws that Chrome 149.0.7827.155 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 33 security flaws, 7 rated critical and 26 high by Google.[1] The 33 critical and high ones are:

FlawSeverityWhat Google calls it
CVE-2026-12437CriticalUse after free in WebShare
CVE-2026-12438CriticalInappropriate implementation in WebView
CVE-2026-12439CriticalUse after free in Digital Credentials
CVE-2026-12440CriticalUse after free in DigitalCredentials
CVE-2026-12441CriticalUse after free in File Input
CVE-2026-12442CriticalUse after free in Passwords
CVE-2026-12443CriticalUse after free in Web Authentication
CVE-2026-12444HighOut of bounds read in Chromoting
CVE-2026-12445HighUse after free in Extensions
CVE-2026-12446HighInsufficient data validation in Passwords
CVE-2026-12447HighHeap buffer overflow in WebRTC
CVE-2026-12448HighInappropriate implementation in WebView
CVE-2026-12449HighUse after free in Chromoting
CVE-2026-12450HighInappropriate implementation in Media
CVE-2026-12451HighUse after free in DigitalCredentials
CVE-2026-12452HighUse after free in Downloads
CVE-2026-12453HighInsufficient validation of untrusted input in Input
CVE-2026-12454HighRace in Safe Browsing
CVE-2026-12455HighUse after free in Tab Strip
CVE-2026-12456HighInsufficient validation of untrusted input in Extensions
CVE-2026-12457HighInsufficient data validation in Extensions
CVE-2026-12458HighIncorrect security UI in Passwords
CVE-2026-12459HighInappropriate implementation in Serial
CVE-2026-12460HighInsufficient policy enforcement in File System Access
CVE-2026-12461HighOut of bounds read in WebRTC
CVE-2026-12462HighUse after free in Media
CVE-2026-12463HighInappropriate implementation in Views
CVE-2026-12464HighUse after free in Browser
CVE-2026-12465HighInsufficient validation of untrusted input in Metrics
CVE-2026-12466HighHeap buffer overflow in WebRTC
and 3 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 149.0.7827.196 or later.

149.0.7827.114 vs 149.0.7827.155

Chrome 149.0.7827.114, released 11 Jun 2026, fixed 27 security flaws. Chrome 149.0.7827.155 fixes 33 security flaws and includes the fixes before it, so going straight to 149.0.7827.155 gets you both.

References

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