Should you update to Chrome 157.0.8103.78?
No: install Chrome 158.0.8127.36 instead. Chrome 157.0.8103.78 is a security update Google released on 11 Nov 2026 for Mac, Windows and Linux. It fixes 83 security flaws, 5 rated critical and 78 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 158.0.8127.36, released 17 Nov 2026, which includes all of its fixes.
Hear about the next Chrome update the day it ships: get the alert below, or add the free HARD extension.
Should you update?
No: install Chrome 158.0.8127.36 instead. Chrome 158.0.8127.36 came out on 17 Nov 2026 and includes every fix in Chrome 157.0.8103.78, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.
Is Chrome 157.0.8103.78 still safe?
Not any more. Chrome 158.0.8127.36 fixes 204 security flaws that Chrome 157.0.8103.78 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 83 security flaws, 5 rated critical and 78 high by Google.[1]
The critical and high fixes83
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-126885 | Critical | Use after free in ServiceWorker |
CVE-2026-126895 | Critical | Use after free in CSS |
CVE-2026-126879 | Critical | Use after free in Layout |
CVE-2026-126846 | Critical | Use after free in Skia |
CVE-2026-126911 | Critical | Use after free in Accessibility |
CVE-2026-126864 | High | Use after free in V8 |
CVE-2026-126889 | High | Off-by-one error in V8 |
CVE-2026-126859 | High | Link following in FileSystem |
CVE-2026-126886 | High | Use after free in Frames |
CVE-2026-126887 | High | Use after free in Animation |
CVE-2026-126870 | High | Uninitialized resource in ANGLE |
CVE-2026-126912 | High | Buffer overflow in Skia |
CVE-2026-126919 | High | Use after free in BrowserTag |
CVE-2026-126878 | High | Information leak in Core |
CVE-2026-126909 | High | Use after free in Passwords |
CVE-2026-126847 | High | Type confusion in V8 |
CVE-2026-126853 | High | Uninitialized resource in Skia |
CVE-2026-126865 | High | Use after free in DOM |
CVE-2026-126916 | High | Integer overflow in V8 |
CVE-2026-126903 | High | Improper state validation in ANGLE |
CVE-2026-126910 | High | Type confusion in V8 |
CVE-2026-126842 | High | Use after free in ANGLE |
CVE-2026-126898 | High | Uninitialized resource in Skia |
CVE-2026-126871 | High | Out of bounds read in Skia |
CVE-2026-126875 | High | Missing authorization in V8 |
CVE-2026-126862 | High | Improper input validation in Core |
CVE-2026-126900 | High | Use after free in CSS |
CVE-2026-126904 | High | Use after free in Compositing |
CVE-2026-126907 | High | Uninitialized resource in Media |
CVE-2026-126851 | High | Use after free in Accessibility |
| and 53 more | ||
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 158.0.8127.36 or later.
157.0.8103.50 vs 157.0.8103.78
Chrome 157.0.8103.50, released 9 Nov 2026, fixed 8 security flaws, one already used in attacks. Chrome 157.0.8103.78 fixes 83 security flaws and includes the fixes before it, so going straight to 157.0.8103.78 gets you both; you never need Chrome 157.0.8103.50 first. It has since been replaced by Chrome 158.0.8127.36.
Every release and the latest version: Chrome updates; everything HARD tracks: Updates.
157.0.8103.50 and 157.0.8103.78 side by side
| Release | 157.0.8103.50 | 157.0.8103.78 |
|---|---|---|
| Released | ||
| Security fixes | 8 | 83 |
| Critical, high | 0, 6 | 5, 78 |
| Used in attacks | 1 | None known |
- Before: Chrome 157.0.8103.50, 9 Nov 2026, 8 security flaws
- After: Chrome 158.0.8127.36, 17 Nov 2026, 204 security flaws
Questions and references
Questions9
When was Chrome 157.0.8103.78 released?
Google released Chrome 157.0.8103.78 on 11 Nov 2026. It has since been replaced by Chrome 158.0.8127.36, released 17 Nov 2026.
What’s new in Chrome 157.0.8103.78?
Google released it as a security update that fixes 83 security flaws, 5 rated critical and 78 high by Google. None of them is known to be used in attacks. This page covers those fixes; Google’s own release notes have its full wording.
Should I update to Chrome 157.0.8103.78?
No: install Chrome 158.0.8127.36 instead. Chrome 158.0.8127.36 includes every fix in Chrome 157.0.8103.78.
Is Chrome 157.0.8103.78 still safe?
Not any more. Chrome 158.0.8127.36 fixes 204 security flaws that Chrome 157.0.8103.78 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.
How long does the Chrome 157.0.8103.78 update take?
A minute or two. Chrome downloads it in the background, and relaunching reopens your tabs.
What is the latest Chrome version?
Chrome 158.0.8127.36, released 17 Nov 2026. Chrome 157.0.8103.78 is not the newest Chrome release any more.
Can I skip Chrome 157.0.8103.78?
Yes, if you go straight to Chrome 158.0.8127.36, which includes every fix in Chrome 157.0.8103.78. Stopping at Chrome 157.0.8103.78 leaves 204 security flaws open that the later updates close.
What is the difference between Chrome 157.0.8103.50 and Chrome 157.0.8103.78?
Chrome 157.0.8103.50, released 9 Nov 2026, fixed 8 security flaws, one already used in attacks. Chrome 157.0.8103.78, released 11 Nov 2026, fixes 83 security flaws and includes the earlier fixes, so installing 157.0.8103.78 straight away covers both.
How do I check my installed Chrome version?
chrome://settings/help shows the version, and says “Chrome is up to date” when it is. Chrome 157.0.8103.78 is the release this page covers; Chrome 158.0.8127.36 replaces it, so the version should say 158.0.8127.36 or later.
References1
- ^ Google. “Stable Channel Update for Desktop”, 11 Nov 2026.

