Should you update to Chrome 154.0.8037.92?
No: install Chrome 157.0.8103.38 instead. Chrome 154.0.8037.92 is a security update Google released on 29 Sep 2026 for Mac, Windows and Linux. It fixes 32 security flaws, 1 rated critical and 25 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 154.0.8037.97, released 2 Oct 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 154.0.8037.92, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.
Is Chrome 154.0.8037.92 still safe?
Not any more. The 8 updates since, up to Chrome 157.0.8103.38, fix 944 security flaws that Chrome 154.0.8037.92 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 32 security flaws, 1 rated critical and 25 high by Google.[1] The 26 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-102331 | Critical | Buffer overflow in ANGLE |
CVE-2026-102317 | High | Improper privilege management in Mojo |
CVE-2026-102312 | High | UI misrepresentation in Omnibox |
CVE-2026-102313 | High | Uninitialized resource in ANGLE |
CVE-2026-102299 | High | Type confusion in V8 |
CVE-2026-102306 | High | Use after free in Bluetooth |
CVE-2026-102307 | High | Uninitialized resource in Dawn |
CVE-2026-102323 | High | Type confusion in V8 |
CVE-2026-102303 | High | Uninitialized resource in GPU |
CVE-2026-102311 | High | Uninitialized resource in GPU |
CVE-2026-102300 | High | Uninitialized resource in WebGPU |
CVE-2026-102326 | High | Type confusion in V8 |
CVE-2026-102316 | High | Use after free in Views |
CVE-2026-102304 | High | Use after free in Passwords |
CVE-2026-102328 | High | Type confusion in V8 |
CVE-2026-102309 | High | Use after free in FullScreen |
CVE-2026-102325 | High | Uninitialized resource in Skia |
CVE-2026-102308 | High | Use after free in Views |
CVE-2026-102301 | High | Out of bounds write in GPU |
CVE-2026-102319 | High | Uninitialized resource in GPU |
CVE-2026-102324 | High | Use after free in PictureInPicture |
CVE-2026-102318 | High | Out of bounds read in WebGL |
CVE-2026-102329 | High | Cross-site scripting in WebUI |
CVE-2026-102315 | High | Uninitialized resource in Media |
CVE-2026-102302 | High | Buffer overflow in V8 |
CVE-2026-102321 | High | Type confusion in V8 |
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 154.0.8037.97 or later.
154.0.8037.57 vs 154.0.8037.92
Chrome 154.0.8037.57, released 22 Sep 2026, fixed 108 security flaws. Chrome 154.0.8037.92 fixes 32 security flaws and includes the fixes before it, so going straight to 154.0.8037.92 gets you both.
- Before: Chrome 154.0.8037.57, 22 Sep 2026, 108 security flaws
- After: Chrome 154.0.8037.97, 2 Oct 2026, 11 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”, 29 Sep 2026.