Should you update to Chrome 149.0.7827.102?
No: install Chrome 157.0.8103.38 instead. Chrome 149.0.7827.102 is a security update Google released on 8 Jun 2026 for Mac, Windows and Linux. It fixes 74 security flaws, 17 rated critical and 55 high by Google.[1] One of them is already being used in attacks.
It has since been replaced by Chrome 149.0.7827.114, released 11 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.102, 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.102 still safe?
Not any more. The 33 updates since, up to Chrome 157.0.8103.38, fix 2,755 security flaws that Chrome 149.0.7827.102 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 74 security flaws, 17 rated critical and 55 high by Google.[1] The 72 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-11628 | Critical | Use after free in Ozone |
CVE-2026-11629 | Critical | Use after free in Ozone |
CVE-2026-11630 | Critical | Use after free in File Input |
CVE-2026-11631 | Critical | Use after free in Aura |
CVE-2026-11632 | Critical | Use after free in TabStrip |
CVE-2026-11633 | Critical | Use after free in Bluetooth |
CVE-2026-11634 | Critical | Use after free in Gamepad |
CVE-2026-11635 | Critical | Use after free in Bluetooth |
CVE-2026-11636 | Critical | Use after free in Autofill |
CVE-2026-11637 | Critical | Use after free in Views |
CVE-2026-11638 | Critical | Use after free in Printing |
CVE-2026-11639 | Critical | Use after free in Compositing |
CVE-2026-11640 | Critical | Integer overflow in libyuv |
CVE-2026-11641 | Critical | Use after free in Bluetooth |
CVE-2026-11642 | Critical | Use after free in Web Apps |
CVE-2026-11643 | Critical | Use after free in Proxy |
CVE-2026-11644 | Critical | Use after free in Views |
CVE-2026-11645 | High | Out of bounds memory access in V8 |
CVE-2026-11646 | High | Use after free in ViewTransitions |
CVE-2026-11647 | High | Use after free in Printing |
CVE-2026-11648 | High | Use after free in FullScreen |
CVE-2026-11649 | High | Use after free in V8 |
CVE-2026-11650 | High | Use after free in V8 |
CVE-2026-11651 | High | Use after free in Network |
CVE-2026-11652 | High | Use after free in Extensions |
CVE-2026-11653 | High | Insufficient validation of untrusted input in Extensions |
CVE-2026-11654 | High | Use after free in CameraCapture |
CVE-2026-11655 | High | Integer overflow in Media |
CVE-2026-11656 | High | Use after free in ServiceWorker |
CVE-2026-11657 | High | Use after free in Payments |
| and 42 more | ||
Used in attacks
This fix closes a flaw that attackers were already using before the update came out, either on CISA’s list of flaws being used in attacks or in Google’s own words.[2]
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.114 or later.
149.0.7827.53 vs 149.0.7827.102
Chrome 149.0.7827.53, released 2 Jun 2026, fixed 429 security flaws. Chrome 149.0.7827.102 fixes 74 security flaws and includes the fixes before it, so going straight to 149.0.7827.102 gets you both.
- Before: Chrome 149.0.7827.53, 2 Jun 2026, 429 security flaws
- After: Chrome 149.0.7827.114, 11 Jun 2026, 27 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”, 8 Jun 2026.
- ^ Cybersecurity and Infrastructure Security Agency. “Known Exploited Vulnerabilities Catalog”.