Should you update to Chrome 150.0.7871.124?
No: install Chrome 157.0.8103.38 instead. Chrome 150.0.7871.124 is a security update Google released on 14 Jul 2026 for Mac, Windows and Linux. It fixes 15 security flaws, 2 rated critical and 12 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 150.0.7871.128, released 16 Jul 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 150.0.7871.124, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.
Is Chrome 150.0.7871.124 still safe?
Not any more. The 25 updates since, up to Chrome 157.0.8103.38, fix 2,199 security flaws that Chrome 150.0.7871.124 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 15 security flaws, 2 rated critical and 12 high by Google.[1] The 14 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-15764 | Critical | Use after free in Ozone |
CVE-2026-15765 | Critical | Use after free in Ozone |
CVE-2026-15766 | High | Uninitialized Use in Skia |
CVE-2026-15767 | High | Heap buffer overflow in libyuv |
CVE-2026-15768 | High | Insufficient policy enforcement in HTML-in-Canvas |
CVE-2026-15769 | High | Insufficient validation of untrusted input in Linux Toolkit Theming |
CVE-2026-15770 | High | Uninitialized Use in V8 |
CVE-2026-15771 | High | Insufficient validation of untrusted input in Media |
CVE-2026-15772 | High | Use after free in GPU |
CVE-2026-15773 | High | Use after free in Core |
CVE-2026-15774 | High | Use after free in Skia |
CVE-2026-15775 | High | Insufficient policy enforcement in V8 |
CVE-2026-15776 | High | Type Confusion in V8 |
CVE-2026-15777 | High | Use after free in UI |
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 150.0.7871.128 or later.
150.0.7871.114 vs 150.0.7871.124
Chrome 150.0.7871.114, released 8 Jul 2026, fixed 27 security flaws. Chrome 150.0.7871.124 fixes 15 security flaws and includes the fixes before it, so going straight to 150.0.7871.124 gets you both.
- Before: Chrome 150.0.7871.114, 8 Jul 2026, 27 security flaws
- After: Chrome 150.0.7871.128, 16 Jul 2026, 7 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”, 14 Jul 2026.