The Chrome 157 update is live on the stable channel, and the headline number is big: 213 security fixes. Google promoted it on November 3, 2026 for Windows, Mac, and Linux. If you haven’t restarted Chrome in a few days, do it now.
Here’s the short version of what matters, straight from Google’s Chrome Releases post.
The essentials, in one glance:
- Released on November 3, 2026 to the stable channel.
- Covers Windows, Mac, and Linux.
- Includes 213 security fixes, with seven listed as critical.
- Rollout is gradual, so it may take days or weeks to reach every device.
What the Chrome 157 update fixes
Chrome updates ship security fixes every time, but 213 in one release is a lot. Google’s notes name seven critical bugs, and most of them are memory problems.
Two sit in Dawn, the component behind Chrome’s WebGPU graphics. One is a buffer overflow tracked as CVE-2026-121156, which earned a $10,000 reward. There is also a use-after-free in WebGL, a memory corruption bug in ANGLE, and use-after-free flaws in Prerender, Geometry, and Core.
Why does that matter to you? Memory bugs in the browser can let a booby-trapped web page run code on your machine. Google doesn’t say any of these are being exploited right now, but the fix is free and takes a minute.
One detail stands out. The Prerender bug, CVE-2026-121035, was reported by Anthropic’s Xinyang Ge, with help from Claude. It’s another sign that AI tools are now finding real browser bugs.
High-severity bugs worth knowing about
Below the critical tier, Google lists several high-severity fixes. These are the ones it highlighted:
- CVE-2026-121107: incorrect authorization in BackgroundFetch, a $10,000 reward.
- CVE-2026-121197: an out-of-bounds read in ANGLE, a $2,000 reward.
- CVE-2026-121082: type confusion in V8, Chrome’s JavaScript engine.
The list is a selection, not everything. Google usually holds back details on some bugs until most users have updated, so the full picture may grow over the next few weeks.
How to get the latest Chrome version
Chrome normally updates itself in the background, but it only finishes once you relaunch. These are the builds to look for:
| Platform | Build number | Where to check |
|---|---|---|
| Windows | 157.0.8103.38/.39 | Menu > Help > About Google Chrome |
| Mac | 157.0.8103.38/.39 | Chrome menu > About Google Chrome |
| Linux | 157.0.8103.38 | Your package manager, then restart Chrome |
Open the menu, go to Help, then About Google Chrome. Chrome will check for the update and show a Relaunch button. Save your tabs first, or let Chrome restore them after the restart.
If the button doesn’t appear, the rollout probably hasn’t reached you yet. Check again tomorrow rather than hunting for a manual download.
A redesigned menu and other changes you may notice
Security is the big story, but one visible change is coming too. According to WindowsForum, citing Google’s Chrome Enterprise release notes, a redesigned three-dot menu will roll out gradually on desktop and ChromeOS.
The same report says Microsoft plans to retire an older sign-in method in Edge 157 and finish moving to OneAuth on Windows. Some Edge users may have to sign in again. That’s a plan, not something I could confirm in Microsoft’s own notes.
Since you’re already tightening up Chrome, it’s a good time to review your saved logins too. Our guide to the Google Password Manager import tool shows how to clean up duplicates. And if you use autofill, see how Chrome’s Gemini autofill works and how to switch it off.
Frequently Asked Questions
Is the Chrome 157 update safe to install?
Yes. It’s a normal stable-channel release from Google, and skipping it leaves 213 known security holes open. Relaunch Chrome once it’s downloaded.
How do I know if I’m running Chrome 157?
Go to Help, then About Google Chrome. The page shows your version number. You want a build starting with 157.0.8103.
Why hasn’t Chrome 157 reached my computer yet?
Google rolls stable releases out in stages over days or weeks. Check About Google Chrome again in a day or two.
Does Chrome 157 work on Android and iPhone?
Google’s post I checked covers desktop only: Windows, Mac, and Linux. Mobile updates are posted separately.
My take: don’t wait on this one. Relaunch Chrome today, confirm you see a 157 build, and move on. A browser patch with this many critical memory bugs is exactly the kind of update worth five minutes of your time.
Leave a Reply