Should you update to Chrome 150.0.7871.114?
No: install Chrome 157.0.8103.38 instead. Chrome 150.0.7871.114 is a security update Google released on 8 Jul 2026 for Mac, Windows and Linux. It fixes 27 security flaws, 2 rated critical and 23 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 150.0.7871.124, released 14 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.114, 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.114 still safe?
Not any more. The 26 updates since, up to Chrome 157.0.8103.38, fix 2,214 security flaws that Chrome 150.0.7871.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, 2 rated critical and 23 high by Google.[1] The 25 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-15112 | Critical | Use after free in Ozone |
CVE-2026-15129 | Critical | Use after free in Views |
CVE-2026-15132 | High | Uninitialized Use in V8 |
CVE-2026-15133 | High | Use after free in InterestGroups |
CVE-2026-15108 | High | Integer overflow in Extensions API |
CVE-2026-15109 | High | Uninitialized Use in ANGLE |
CVE-2026-15110 | High | Use after free in Extensions |
CVE-2026-15111 | High | Use after free in Views |
CVE-2026-15113 | High | Use after free in Autofill |
CVE-2026-15114 | High | Out of bounds read and write in Codecs |
CVE-2026-15115 | High | Insufficient validation of untrusted input in WebAppInstalls |
CVE-2026-15116 | High | Use after free in Actor |
CVE-2026-15117 | High | Use after free in Payments |
CVE-2026-15118 | High | Use after free in Input |
CVE-2026-15119 | High | Inappropriate implementation in GetUserMedia |
CVE-2026-15120 | High | Use after free in Core |
CVE-2026-15121 | High | Use after free in WebRTC |
CVE-2026-15122 | High | Insufficient validation of untrusted input in Codecs |
CVE-2026-15123 | High | Insufficient data validation in DOM |
CVE-2026-15124 | High | Insufficient policy enforcement in Passwords |
CVE-2026-15125 | High | Inappropriate implementation in Forms |
CVE-2026-15126 | High | Use after free in Forms |
CVE-2026-15127 | High | Inappropriate implementation in WebGL |
CVE-2026-15128 | High | Inappropriate implementation in Forms |
CVE-2026-15130 | High | Insufficient policy enforcement in Navigation |
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.124 or later.
150.0.7871.100 vs 150.0.7871.114
Chrome 150.0.7871.100, released 7 Jul 2026, fixed 0 security flaws. Chrome 150.0.7871.114 fixes 27 security flaws and includes the fixes before it, so going straight to 150.0.7871.114 gets you both.
- Before: Chrome 150.0.7871.100, 7 Jul 2026, 0 security flaws
- After: Chrome 150.0.7871.124, 14 Jul 2026, 15 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 Jul 2026.