Should you update to Chrome 156.0.8078.79?
No: install Chrome 157.0.8103.38 instead. Chrome 156.0.8078.79 is a security update Google released on 29 Oct 2026 for Mac, Windows and Linux. It fixes 21 security flaws, 1 rated critical and 19 high by Google.[1] None of them is known to be used in attacks.
It has since been replaced by Chrome 157.0.8103.38, released 3 Nov 2026, which includes all of its fixes. If you’re on an older version, install that instead.
Should you update?
No: install Chrome 157.0.8103.38 instead. Chrome 157.0.8103.38 came out on 3 Nov 2026 and includes every fix in Chrome 156.0.8078.79, so there’s no reason to stop at this one. Software Update offers the newest version your device can run.
Is Chrome 156.0.8078.79 still safe?
Not any more. Chrome 157.0.8103.38 fixes 213 security flaws that Chrome 156.0.8078.79 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 21 security flaws, 1 rated critical and 19 high by Google.[1] The 20 critical and high ones are:
| Flaw | Severity | What Google calls it |
|---|---|---|
CVE-2026-76024 | Critical | Use after free in MediaStream |
CVE-2026-76025 | High | Incorrect authorization in FileSystem |
CVE-2026-76026 | High | Origin validation error in Autofill |
CVE-2026-76027 | High | Information loss in CacheStorage |
CVE-2026-76028 | High | Incorrect authorization in FileSystem |
CVE-2026-76029 | High | Improper input validation in Network |
CVE-2026-76030 | High | Incorrect authorization in FileSystem |
CVE-2026-76031 | High | Incorrect authorization in Input |
CVE-2026-119260 | High | Use after free in Frames |
CVE-2026-119261 | High | Buffer overflow in Skia |
CVE-2026-119262 | High | Out of bounds write in V8 |
CVE-2026-119263 | High | Use after free in GarbageCollection |
CVE-2026-119264 | High | Use after free in Dawn |
CVE-2026-119265 | High | Incorrect reference resolution in Quota |
CVE-2026-119266 | High | Incorrect reference resolution in Quota |
CVE-2026-119267 | High | Use after free in DOM |
CVE-2026-119268 | High | Use after free in Editing |
CVE-2026-119269 | High | Incorrect authorization in Blink |
CVE-2026-119270 | High | Incorrect reference resolution in CacheStorage |
CVE-2026-119271 | High | Uninitialized resource in Skia |
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 157.0.8103.38 or later.
156.0.8078.73 vs 156.0.8078.79
Chrome 156.0.8078.73, released 27 Oct 2026, fixed 52 security flaws. Chrome 156.0.8078.79 fixes 21 security flaws and includes the fixes before it, so going straight to 156.0.8078.79 gets you both.
- Before: Chrome 156.0.8078.73, 27 Oct 2026, 52 security flaws
- After: Chrome 157.0.8103.38, 3 Nov 2026, 213 security flaws
- Chrome updates, every release and the latest version
- Updates, the latest version of everything HARD tracks
References
- ^ Google. “Stable Channel Update for Desktop”, 29 Oct 2026.