Chrome 157 Update: 213 Security Fixes, 7 Critical — How to Install It Now
Google has released Chrome 157 with 213 security fixes, seven rated Critical. Here are the new versions for Windows, Mac, Linux and Android and how to install the update now.
Image: TeQBlogs
The Chrome 157 update is now rolling out to the stable channel, and it is one of the biggest security releases Google has shipped for its browser: 213 security fixes, seven of them rated Critical. Google released it on 3 November 2026 as version 157.0.8103.38/.39 for Windows and Mac, 157.0.8103.38 for Linux, and 157.0.8103.38 for Android. Open Chrome’s About page and click Relaunch today rather than waiting for the automatic update.
Quick summary
- What: Chrome 157 promoted to the stable channel on 3 November 2026.
- Security: 213 fixes — 7 Critical, 77 High, 75 Medium and 54 Low, as listed in Google’s release note.
- Versions: 157.0.8103.38/.39 (Windows, Mac), 157.0.8103.38 (Linux and Android).
- Exploits: Google’s note does not say any of these bugs are being exploited in the wild.
- Rollout: “over the coming days/weeks” on desktop, and on Google Play “over the next few days” for Android.
- Action: Menu → Help → About Google Chrome → Relaunch.
What is in the Chrome 157 update?
Chrome 157 is a regular milestone release, but its security list is unusually long. Google’s stable-channel note for desktop lists 213 security fixes, along with “a number of fixes and improvements” whose full list is in the Chromium change log. Google says it will describe new features in separate Chrome and Chromium blog posts, so this release is mainly about patching.
Also read: WhatsApp Guest Calling: How to Invite Anyone to a Call, Even Without WhatsApp
For Android, Google released Chrome 157 (157.0.8103.38) on the same day. Its Android note says the release “includes stability and performance improvements” and that Android builds carry the same security fixes as the matching desktop release unless otherwise noted.
| Platform | Chrome 157 version | How it reaches you |
|---|---|---|
| Windows | 157.0.8103.38/.39 | Automatic, or About Google Chrome → Relaunch |
| macOS | 157.0.8103.38/.39 | Automatic, or About Google Chrome → Relaunch |
| Linux | 157.0.8103.38 | Your distribution’s package manager or Google’s repository |
| Android | 157.0.8103.38 | Google Play, over the next few days |
The seven Critical bugs fixed
Critical is Google’s highest severity rating. All seven Critical bugs below are memory-safety flaws (buffer overflows, memory corruption and use-after-free), the kind of bug attackers often try to chain into code execution through a malicious web page. Google keeps full bug details restricted until most users have updated.
| CVE | Component | Type of flaw |
|---|---|---|
| CVE-2026-121156 | Dawn (WebGPU) | Buffer overflow |
| CVE-2026-121247 | Dawn (WebGPU) | Buffer overflow |
| CVE-2026-121229 | ANGLE (graphics) | Memory corruption |
| CVE-2026-121246 | WebGL | Use after free |
| CVE-2026-121035 | Prerender | Use after free |
| CVE-2026-121203 | Geometry | Use after free |
| CVE-2026-121126 | Core | Use after free |
Four of the seven sit in the graphics stack — Dawn, ANGLE and WebGL — which turns web code into GPU work. The High-severity list adds 77 more bugs, including several type-confusion flaws in V8, Chrome’s JavaScript engine, and multiple bugs in PDFium, the built-in PDF viewer.
AI tools found a noticeable share of the bugs
A striking detail in this release note is who reported the bugs. By our count of Google’s list, 14 entries are credited to researchers at Anthropic “assisted by Claude”, and 7 entries are credited to OpenAI Codex Security. One of the seven Critical bugs, CVE-2026-121035 in Prerender, is among the entries credited to Anthropic with Claude’s help.
Google’s own teams reported a large part of the rest, with the remaining entries from independent researchers who earn rewards through Chrome’s bug bounty. The takeaway for ordinary users is simple: AI-assisted bug hunting is now finding browser flaws at scale, which makes regular updates even more important.
How to install the Chrome 157 update
Chrome updates itself in the background, but the new version only takes effect after the browser restarts. Here is how to apply it right away. If you are also patching your phone this week, our guide to the Android November security update covers that side.
On Windows, Mac or Linux
- Open Chrome.
- At the top right, click the three-dot More menu.
- Choose Help → About Google Chrome. Chrome checks for updates as soon as this page opens.
- Click Relaunch. Your tabs and windows reopen automatically, but Incognito windows do not.
- Check that the version shown under “Google Chrome” starts with 157.0.8103.
If you don’t see a Relaunch button, you’re already on the latest version available to you. Because the rollout is staged, some PCs may get 157 a few days later; come back to the About page later.
On Android
- Open the Google Play Store.
- Search for Google Chrome.
- Tap Update if it appears. If you only see “Open”, the update hasn’t reached your phone yet.
What if Chrome won’t update?
Most update failures come from a pending restart, an administrator policy or an old operating system. Try these checks in order:
- Close every Chrome window, including ones in the background, then reopen Chrome and visit the About page again.
- Office or school PC? Your IT team may control updates through policy, and Chrome will show that the browser is managed by your organisation. Ask them when 157 will be deployed.
- Restart the computer if the update seems stuck.
- Linux users should update through their package manager rather than the About page.
For small businesses that run dozens of PCs, a browser patch like this is a good test of whether updates actually reach every machine. If you don’t have a process for that yet, a managed IT service can handle patching and reporting across devices.
Should Indian users worry?
There is no sign of an active attack, so there is no need to panic, but there is good reason to update promptly. Chrome is used by a very large share of Indian desktop and Android users, and once a patch is public, attackers can study the code changes to work out the flaws. That is why Google keeps details private until most users are updated.
Along with updating, keep the basics in place: avoid unknown download links, keep Enhanced protection on in Chrome’s Safe Browsing settings if you want stronger warnings, and learn the signs of a fake site — our guide on how to check websites for fraud explains them. iPhone users who also received Apple’s recent alerts can read our explainer on the Apple threat notification.
Frequently asked questions
What is the latest version of Chrome?
As of 3 November 2026, the stable version is Chrome 157: 157.0.8103.38/.39 on Windows and Mac, and 157.0.8103.38 on Linux and Android. Google is rolling it out gradually over days or weeks.
How many security fixes are in Chrome 157?
Google’s release note lists 213 security fixes. Seven are rated Critical, 77 High, 75 Medium and 54 Low.
Are the Chrome 157 bugs being exploited?
Google’s release note does not say that any of the fixed bugs are being exploited in the wild. Updating promptly is still recommended because patched flaws become easier to study once a fix is public.
How do I check my Chrome version?
Open the three-dot menu, then Help → About Google Chrome. The version appears under the “Google Chrome” heading; it should start with 157.0.8103 after the update.
Bottom line
Chrome 157 fixes 213 security bugs, including seven Critical memory-safety flaws, and it is rolling out now. It takes less than a minute to apply: open About Google Chrome, click Relaunch, and update the Android app from Google Play when it appears.
Sources
- Google Chrome Releases — Stable Channel Update for Desktop (3 November 2026)
- Google Chrome Releases — Chrome for Android Update (3 November 2026)
- Google Chrome Help — Update Google Chrome
About The Author
