Should you update to Chrome 149.0.7827.114?
No: install Chrome 157.0.8103.38 instead. Chrome 149.0.7827.114 is a security update Google released on 11 Jun 2026 for Mac, Windows and Linux. It fixes 27 security flaws, 5 rated critical and 22 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 149.0.7827.155, released 16 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.114, 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.114 still safe?
Not any more. The 32 updates since, up to Chrome 157.0.8103.38, fix 2,728 security flaws that Chrome 149.0.7827.114 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 27 security flaws, 5 rated critical and 22 high by Google.[1] The 27 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-12007 | Critical | Use after free Core |
CVE-2026-12008 | Critical | Use after free DigitalCredentials |
CVE-2026-12009 | Critical | Insufficient validation of untrusted input Accessibility |
CVE-2026-12010 | Critical | Heap buffer overflow GPU |
CVE-2026-12011 | Critical | Use after free WebMIDI |
CVE-2026-12012 | High | Use after free Network |
CVE-2026-12014 | High | Use after free Cast |
CVE-2026-12015 | High | Use after free Autofill |
CVE-2026-12016 | High | Insufficient validation of untrusted input DevTools |
CVE-2026-12017 | High | Insufficient validation of untrusted input Extensions |
CVE-2026-12018 | High | Inappropriate implementation Mojo |
CVE-2026-12019 | High | Out of bounds write Codecs |
CVE-2026-12020 | High | Use after free Autofill |
CVE-2026-12022 | High | Race Safe Browsing |
CVE-2026-12023 | High | Use after free GPU |
CVE-2026-12024 | High | Insufficient policy enforcement DevTools |
CVE-2026-12025 | High | Insufficient validation of untrusted input Network |
CVE-2026-12026 | High | Out of bounds read Video |
CVE-2026-12027 | High | Insufficient policy enforcement Headless |
CVE-2026-12028 | High | Use after free GPU |
CVE-2026-12029 | High | Use after free Video |
CVE-2026-12030 | High | Heap buffer overflow GPU |
CVE-2026-12031 | High | Inappropriate implementation Views |
CVE-2026-12032 | High | Inappropriate implementation Passwords |
CVE-2026-12033 | High | Out of bounds read VideoCapture |
CVE-2026-12034 | High | Insufficient validation of untrusted input Linux Toolkit Theming |
CVE-2026-12035 | High | Use after free Views |
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.155 or later.
149.0.7827.102 vs 149.0.7827.114
Chrome 149.0.7827.102, released 8 Jun 2026, fixed 74 security flaws, one already used in attacks. Chrome 149.0.7827.114 fixes 27 security flaws and includes the fixes before it, so going straight to 149.0.7827.114 gets you both.
- Before: Chrome 149.0.7827.102, 8 Jun 2026, 74 security flaws
- After: Chrome 149.0.7827.155, 16 Jun 2026, 33 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”, 11 Jun 2026.