Should you update to Chrome 149.0.7827.53?
No: install Chrome 157.0.8103.38 instead. Chrome 149.0.7827.53 is a security update Google released on 2 Jun 2026 for Mac, Windows and Linux. It fixes 429 security flaws, 22 rated critical and 87 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 149.0.7827.102, released 8 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.53, 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.53 still safe?
Not any more. The 34 updates since, up to Chrome 157.0.8103.38, fix 2,829 security flaws that Chrome 149.0.7827.53 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 429 security flaws, 22 rated critical and 87 high by Google.[1] The 109 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-10881 | Critical | Out of bounds read and write in ANGLE |
CVE-2026-10882 | Critical | Use after free in Network |
CVE-2026-10883 | Critical | Out of bounds write in ANGLE |
CVE-2026-10884 | Critical | Use after free in Chromecast |
CVE-2026-10885 | Critical | Use after free in Chrome for iOS |
CVE-2026-10886 | Critical | Use after free in FileSystem |
CVE-2026-10887 | Critical | Use after free in Chromoting |
CVE-2026-10888 | Critical | Use after free in Cast Streaming |
CVE-2026-10889 | Critical | Out of bounds read in ANGLE |
CVE-2026-10890 | Critical | Use after free in Cast |
CVE-2026-10891 | Critical | Use after free in GFX |
CVE-2026-10892 | Critical | Out of bounds write in GPU |
CVE-2026-10893 | Critical | Use after free in Chromoting |
CVE-2026-10894 | Critical | Use after free in Printing |
CVE-2026-10895 | Critical | Use after free in Ozone |
CVE-2026-10896 | Critical | Use after free in Chrome for iOS |
CVE-2026-10897 | Critical | Out of bounds write in GPU |
CVE-2026-10898 | Critical | Stack buffer overflow in GPU |
CVE-2026-10899 | Critical | Use after free in Ozone |
CVE-2026-10900 | Critical | Use after free in Passwords |
CVE-2026-10901 | Critical | Use after free in Passwords |
CVE-2026-10902 | Critical | Use after free in Ozone |
CVE-2026-10903 | High | Use after free in WebRTC |
CVE-2026-10904 | High | Inappropriate implementation in V8 |
CVE-2026-10905 | High | Use after free in Network |
CVE-2026-10906 | High | Use after free in WebAuthentication |
CVE-2026-10907 | High | Out of bounds write in ANGLE |
CVE-2026-10908 | High | Use after free in FullScreen |
CVE-2026-10909 | High | Use after free in Dawn |
CVE-2026-10910 | High | Type Confusion in V8 |
| and 79 more | ||
How to update, and how long it takes
A minute or two. Chrome downloads it in the background, and relaunching reopens your tabs.
- 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.
- Click Relaunch.Chrome reopens your tabs. Until you relaunch, the old, unfixed version keeps running.
- 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.102 or later.
Before and after
- After: Chrome 149.0.7827.102, 8 Jun 2026, 74 security flaws
- Chrome updates, every release and the latest version
- Updates, the latest version of everything HARD tracks
References
- ^ Google. “Stable Channel Update for Desktop”, 2 Jun 2026.