Google Chrome 157 update is now rolling out, and Unfite is here to explain it in simple words. Google has moved Chrome 157 to the stable channel for Windows, Mac and Linux, and the update brings 213 security fixes. That is a large number, so this is not a small, routine update. It is mainly a security update, and users should install it when it becomes available on their device.
Image Credit: Google — Official Chrome image
The most important point is simple. Seven of the 213 fixes are rated critical. The rest cover a wide range of other security issues. Google has NOT said any flaw is being exploited in the wild. In other words, there is no confirmed report in this release that attackers are already using these flaws. Still, critical flaws are fixed first for a reason, and waiting too long is never a good idea.
Google Chrome 157 Update: What Is New
The google chrome 157 update focuses on safety and stability. Google says the new stable version contains a number of fixes and improvements. A list of changes is available in the official log, and Google has also said to watch for upcoming Chrome and Chromium blog posts about new features and larger efforts delivered in version 157. For most users, however, the headline is security, not a flashy new feature.
The rollout is staged. Google says the update will roll out over the coming days and weeks. That means not every user will see it at the same time. If your browser still shows an older version today, it does not always mean something is wrong. It may simply mean the staged rollout has not reached your device yet. Keep checking, and install it as soon as it appears.
Google Chrome 157 Version Numbers
Version numbers matter because they tell you whether you are on the new, fixed version. Use the table below to check your device.
| Platform | Chrome 157 Stable Version |
|---|---|
| Windows | 157.0.8103.38 / .39 |
| Mac | 157.0.8103.38 / .39 |
| Linux | 157.0.8103.38 |
| Android | Rolling out in stages; check the Play Store for the latest Chrome 157 build for your device |
On a computer, you can check your version in Chrome itself. Open the menu, go to Help, then About Google Chrome. Chrome will show the version number and check for an update. On Android, the version is shown in the Play Store listing and in the app settings on many phones.
The 7 Critical Flaws in Google Chrome 157, Explained Simply
Google lists seven critical flaws in this release. Each one has a CVE number, which is a public ID for a known security issue. Below, each flaw is explained in plain English, without technical jargon.
1. CVE-2026-121156: Buffer Overflow in Dawn
Dawn is a part of Chrome that helps draw graphics. A buffer overflow happens when a program writes more data than a safe space can hold. That can confuse the browser and, in serious cases, let an attacker take control. Google rates this flaw critical, so the fix matters.
2. CVE-2026-121229: Memory Corruption in ANGLE
ANGLE helps Chrome show graphics on different devices. Memory corruption means the browser handles stored data in a wrong or unsafe way. When memory is corrupted, the browser can crash or behave in ways an attacker may try to use. This fix closes that risk.
3. CVE-2026-121246: Use After Free in WebGL
WebGL lets websites show 3D graphics in the browser. Use after free means the browser tries to use a piece of memory after it has already been freed. That is a classic browser security problem, because the freed space may be reused in an unsafe way. The update fixes it.
4. CVE-2026-121035: Use After Free in Prerender
Prerender helps Chrome prepare a page before you fully open it, so it feels faster. Here, the same use-after-free problem appeared in that preparation step. If a page is prepared in an unsafe way, it can create a security risk, even before you click anything else. Chrome 157 fixes that step.
5. CVE-2026-121247: Buffer Overflow in Dawn
This is a second critical buffer overflow in Dawn. It is a separate flaw from the first one, even though it affects the same graphics area. Fixing both matters, because one fix alone would still leave the other problem open. Together, the two fixes make graphics handling safer.
6. CVE-2026-121203: Use After Free in Geometry
Geometry in this context relates to how Chrome handles shapes and layout data. A use-after-free flaw here can again let the browser touch memory it should no longer use. That may cause crashes or, in the worst case, open a path for attack. The new version closes this flaw.
7. CVE-2026-121126: Use After Free in Core
Core is a central part of the browser. A use-after-free flaw in a core area is serious because it can affect many parts of Chrome, not just one feature. This is one reason Google marks it critical. Installing Chrome 157 removes this known risk from your browser.
What About the Other 206 Security Fixes?
After the seven critical flaws, the remaining fixes are rated high, medium or low. They cover many parts of Chrome, including graphics, media, PDF handling, extensions, permissions, file access and the browser interface. Some fix memory problems, some fix checks that were missing, and some fix cases where a website could show misleading information.
You do not need to read all 213 entries to stay safe. The practical lesson is the same for every user. Update the browser, restart it when asked, and keep automatic updates turned on. That single habit protects you from most of the issues listed in a large security release like this one.
Google Chrome 157 Update for Android
Android users are also part of this update. The google chrome 157 update is rolling out for Android as well, and Android users should watch for the update in the Google Play Store. Because Android phones and tablets vary by maker and model, the update may not arrive on every device on the same day.
To check on Android, open the Google Play Store, search for Chrome, and open the Chrome app page. If an Update button is shown, tap it. If you see only Open, your phone is either already up to date or the new version has not reached you yet. You can also turn on auto-update for Chrome in the Play Store, so future security fixes install without manual checks.
At Unfite, we recommend Android users not delay security updates for a browser. Chrome is used for banking, email, shopping and work on many phones. A browser flaw can affect any website you open, so a prompt update is one of the easiest safety steps you can take.
How to Update Google Chrome
Follow these simple steps for your device.
- On Windows or Mac, open Chrome, click the three-dot menu, then go to Help and About Google Chrome.
- Chrome will check for an update and show your version number.
- If an update is available, let it download and install, then relaunch Chrome when asked.
- On Linux, update Chrome through your system update tool or package manager, as you normally update apps.
- On Android, open the Play Store, search for Chrome, and tap Update if it is shown.
- After updating, check the version again to confirm you are on Chrome 157.
If the update is not shown yet, wait and check again later. Remember, rollout is staged over days and weeks. Do not download Chrome from unknown websites to get it faster. Use only the official Chrome update inside the browser, the Play Store, or the official Google Chrome website.
ChromeOS 157: What We Know So Far
ChromeOS users should note one clear point. ChromeOS 157 Stable had not been posted yet at the time of this update. That does not mean Chromebooks are ignored. It simply means the desktop announcement covered Windows, Mac and Linux, and a separate ChromeOS post had not appeared yet. Chromebook users should keep checking for their own system update and avoid assuming the desktop version numbers apply to ChromeOS.
For more detail on other Google apps, Unfite readers can also read our post on Google Messages phone contacts new icons. It is a useful reminder that Google updates its apps often, and small changes can arrive alongside larger security releases.
Frequently Asked Questions About the Google Chrome 157 Update
What is the Google Chrome 157 update?
It is the stable release of Chrome 157 for Windows, Mac, Linux and Android. It includes 213 security fixes, including seven critical flaws, and it is rolling out in stages.
Is Google Chrome 157 safe to install?
Yes. It is the official stable release from Google, and it fixes known security issues. Installing it from Chrome itself or the Play Store is the safe way to update.
Are any of the flaws being exploited by hackers?
Google has NOT said any flaw is being exploited. The release does not claim active exploitation. Still, critical flaws should be fixed quickly, because details can become more widely known over time.
Why is Chrome 157 not showing on my device yet?
The rollout is staged over days and weeks, so it reaches users in groups. Check again later, and make sure automatic updates are turned on for Chrome and for your device.
How can I check my Chrome version?
On a computer, go to the three-dot menu, then Help, then About Google Chrome. On Android, check the Chrome page in the Google Play Store. If you are on 157.0.8103.38 or .39 on desktop, you have the new stable version.
Final Thoughts
The google chrome 157 update is a security-first release. With 213 fixes and seven critical flaws, it is worth installing as soon as it reaches your device. The steps are simple, the update is free, and the benefit is clear. Unfite will keep following Google Chrome updates and explain them in simple English, so check back for the next stable release and for news on ChromeOS 157 when it is posted.
Source: Chrome Releases blog: Stable Channel Update for Desktop