Should you update to Chrome 149.0.7827.196?
No: install Chrome 157.0.8103.38 instead. Chrome 149.0.7827.196 is a security update Google released on 23 Jun 2026 for Mac, Windows and Linux. It fixes 18 security flaws, 4 rated critical and 14 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 149.0.7827.200, released 25 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.196, 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.196 still safe?
Not any more. The 30 updates since, up to Chrome 157.0.8103.38, fix 2,677 security flaws that Chrome 149.0.7827.196 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 18 security flaws, 4 rated critical and 14 high by Google.[1] The 18 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-13028 | Critical | Use after free in WebGL |
CVE-2026-13032 | Critical | Use after free in WebGL |
CVE-2026-13033 | Critical | Out of bounds read in Blink>InterestGroups |
CVE-2026-13038 | Critical | Use after free in Autofill |
CVE-2026-13021 | High | Inappropriate implementation in DeviceBoundSessionCredentials |
CVE-2026-13022 | High | Inappropriate implementation in Autofill |
CVE-2026-13023 | High | Uninitialized Use in GPU |
CVE-2026-13024 | High | Insufficient validation of untrusted input in Navigation |
CVE-2026-13025 | High | Insufficient validation of untrusted input in DevTools |
CVE-2026-13026 | High | Use after free in Digital Credentials |
CVE-2026-13027 | High | Use after free in FileSystem |
CVE-2026-13029 | High | Use after free in Web Authentication |
CVE-2026-13030 | High | Uninitialized Use in GPU |
CVE-2026-13031 | High | Use after free in Blink |
CVE-2026-13034 | High | Inappropriate implementation in Passwords |
CVE-2026-13035 | High | Use after free in Bluetooth |
CVE-2026-13036 | High | Use after free in Blink |
CVE-2026-13037 | High | Use after free in WebView |
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.200 or later.
149.0.7827.155 vs 149.0.7827.196
Chrome 149.0.7827.155, released 16 Jun 2026, fixed 33 security flaws. Chrome 149.0.7827.196 fixes 18 security flaws and includes the fixes before it, so going straight to 149.0.7827.196 gets you both.
- Before: Chrome 149.0.7827.155, 16 Jun 2026, 33 security flaws
- After: Chrome 149.0.7827.200, 25 Jun 2026, 3 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”, 23 Jun 2026.