Google packed 213 security fixes into one Chrome release on November 3, 2026, and seven of them carry the Critical label. If your browser still reports version 156 or older, open the menu, choose Help, then About Google Chrome, let it download, and press Relaunch. It’s a short job. Do it today rather than next week.
How to check that you’re on Chrome 157
- Click the three dot menu in the top right corner of Chrome.
- Choose Help, then About Google Chrome. You can also type chrome://settings/help into the address bar.
- Wait while Chrome looks for the update. It starts the download by itself.
- Press Relaunch when the button appears. Your open tabs normally come back.
You want to see 157.0.8103.38 or newer. On Windows and Mac, Google’s post lists both .38 and .39, so either ending is fine. If you see 158, you got Google’s early rollout, and that also includes the fixes.
| Where you use Chrome | Version in Google’s post | How to get it |
|---|---|---|
| Windows | 157.0.8103.38 or .39 | Help, About Google Chrome, Relaunch |
| Mac | 157.0.8103.38 or .39 | Same menu, then Relaunch |
| Linux | 157.0.8103.38 | Your package manager |
| Android | 157.0.8103.38 | Google Play, over the next few days |
| iPhone and iPad | Not listed in the desktop post | App Store |
What Google actually fixed
Google published the list in its Chrome Releases blog. The seven Critical entries are all memory bugs, and four of the seven sit in graphics code. Two are buffer overflows in Dawn, the part of Chrome that handles WebGPU. One is memory corruption in ANGLE. One is a use after free in WebGL. The other three are use after free bugs in Prerender, Geometry and Core.
A use after free means the browser keeps touching memory it already gave back. An attacker who controls a web page can sometimes steer that mistake into running their own code. Google has not published how any of these could be abused, and I’m not going to guess. The honest summary is that these are the bug types that browser makers treat as serious, and they were fixed.
The High rated group is much longer. It includes incorrect authorization in BackgroundFetch, which earned a $10,000 reward, plus type confusion bugs in V8 (Chrome’s JavaScript engine) and memory bugs in PDFium, the built in PDF viewer. Opening a PDF in a browser tab is something most people do without thinking, which is a decent reason not to postpone this one.
Reward amounts are only shown for some entries. Among the Critical bugs, one Dawn report from an outside researcher paid $10,000 and the ANGLE report paid $1,000. Bugs that Google found itself list no payout.
Should you worry?
Be careful, not alarmed. I didn’t see any note in the release post saying an exploit is circulating, and Google says it holds bug details back until most users have the fix. Nobody outside Google can tell you today whether anyone is trying these bugs. That uncertainty is the reason to update rather than a reason to relax.
Chrome updates itself quietly on most computers, but only when you close and reopen the browser. Plenty of people keep the same window going for weeks. If that’s you, the fix may be downloaded and sitting unused. The Relaunch button is the whole job.
Why Chrome might still show 156
Google sends stable releases out in stages. A check that says “up to date” can be accurate for your computer and still behind what Google has released. Try again in a day. If you manage computers for a family member or a small office, check each one rather than assuming the rollout reached everyone.
Version numbers may also move faster than usual this week. Google’s blog shows Chrome 158 reaching a small share of Windows users as an early stable build on November 4, one day after 157. Most people will land on 157 first.
Chrome is not the only browser involved
Edge, Brave, Opera and Vivaldi share the Chromium engine, and Chromium bugs often matter to them as well. They publish their own fixes on their own timeline, so check the About page in each one you use. I haven’t verified when each vendor ships the November patches.
The credits in Google’s list are also worth a look. Several entries name Anthropic researchers “assisted by Claude” and others name OpenAI Codex Security, so AI assisted bug hunting is now showing up in routine Chrome advisories. The post doesn’t say how much of any finding was automated.
The same habit applies on other devices. Our notes on the Windows 11 24H2 end of support and the November 2026 Android security patch cover the system level versions of this advice.
Chrome 157 update: common questions
Is Chrome 157 safe to install?
Yes. It is the regular stable release that Google promoted on November 3, 2026, and it is the version carrying the security fixes. Staying on an older build is the riskier choice.
Do I have to restart Chrome after the update?
Yes. Chrome downloads the update in the background, but the old version keeps running until you relaunch. If a Relaunch button or a colored arrow sits next to your profile picture, that is the sign a finished update is waiting.
Are these bugs being used in attacks?
Google’s release post does not say so, and the report from Cyber Security News says the same. Critical describes how bad a flaw could be, not that someone is already abusing it. Google also keeps bug details restricted until most people have updated.
Chrome says it is up to date but shows version 156. Why?
Google rolls stable releases out in waves over days or weeks, so the check can honestly report that nothing newer has reached you yet. Check again tomorrow. Chrome 158 also went to a small group as an early stable release on November 4, so version numbers can jump sooner than usual.
How do I update Chrome on my phone?
On Android, open Google Play, search for Chrome and tap Update. Google lists 157.0.8103.38 for Android and says it becomes available over the next few days. On iPhone and iPad, update Chrome from the App Store. The post we checked does not list an iOS version number.
Do Edge, Brave and other browsers need updating too?
They are built on Chromium, but each company ships its own releases on its own schedule. Open each browser’s About page and install whatever it offers. We did not check their release dates for this round.
Sources
- Stable Channel Update for Desktop, Chrome Releases, November 3, 2026
- Chrome Releases blog, Android and early stable 158 posts, November 3 and 4, 2026
- Cyber Security News report on the Chrome 157 release, November 4, 2026
I read Google’s release post on November 5, 2026. The full list of 213 fixes is longer than the highlights above, and Google may add details later.
