Google’s Chrome 157 security update fixes 83 security flaws, and every one of them is rated Critical or High, according to the company’s release notice as reported by CybersecurityNews and SecurityOnline. The update, released on 11 November, takes Chrome to version 157.0.8103.78 for Windows, Mac and Linux, with 157.0.8103.79 also listed for Windows and Mac. Google has not reported any of the 83 flaws as exploited in the wild.
That last point matters. This is a large batch, not an emergency patch. Two days earlier, Google shipped a nine-fix update for an actively exploited zero-day, CVE-2026-125350. Google has not reported active exploitation for this batch, which is exactly why it is easy to ignore, and exactly why you should not.
What the five critical Chrome 157 flaws are
All five critical flaws are use-after-free bugs (CWE-416). Google lists them in its release notice, and CybersecurityNews and SecurityOnline both carry the same five CVE identifiers, components and report dates.
| CVE | Component | Reported by | Reported |
|---|---|---|---|
| CVE-2026-126885 | ServiceWorker | Xinyang Ge | 2 Oct 2026 |
| CVE-2026-126895 | CSS | Xinyang Ge | 19 Oct 2026 |
| CVE-2026-126879 | Layout | Xinyang Ge | 22 Oct 2026 |
| CVE-2026-126846 | Skia | 2 Nov 2026 | |
| CVE-2026-126911 | Accessibility | Andrew Boni | 2 Nov 2026 |
Three of the five were reported by a single researcher, Xinyang Ge, our own count from the list above. The only monetary bounty disclosed in the notice is $4,000 to Jihyeon Jeong of Seoul National University’s Compsec Lab for a high-severity V8 use-after-free flaw, CVE-2026-126864, reported on 30 September, according to SecurityOnline. Every other listed reward is shown as not applicable or still pending.
The five critical flaws took between nine and 40 days to reach users after they were reported. The first, the ServiceWorker bug, was reported on 2 October, 40 days before the patch; the last two, Skia and Accessibility, were reported on 2 November, nine days before it. That is our own timeline from the report dates in Google’s notice.
The remaining 78 high-severity fixes span V8, Skia, ANGLE, Media, Extensions, FileSystem, PDF, Site Isolation, DOM, Layout, Core, GPU and Network, according to the CVE table published by CybersecurityNews. Our own count from that table puts 31 of the 83 fixes, 37.3 percent, in just two components: Skia with 16 and V8 with 15.
One high-severity flaw stands out for Mac users: CVE-2026-126902, an incorrect reference resolution flaw in the Browser component on macOS, according to the CVE table published by CybersecurityNews. One outlet, Reef Sentinel, describes it as a possible Mac sandbox escape in the privileged Browser process, but that reading is unverified, and the same source says it cannot be triggered on its own without a renderer compromise first.
Chrome 157 security update: three releases, 305 fixes in eight days
This is the third Chrome 157 security release in eight days, and the numbers add up fast. Google shipped 213 fixes when Chrome 157 launched on 3 November, then nine fixes on 9 November for the exploited zero-day, and now 83 more on 11 November. That is 305 security fixes across three releases in eight days, our own calculation from Google’s three figures.
The 83-fix batch is 61 percent smaller than the 213-fix launch, 130 fewer fixes, but it is 9.2 times the size of the nine-fix emergency patch. The more striking difference is severity. At launch, 84 of the 213 fixes, 39.4 percent, were rated Critical or High. In this batch, all 83 are, 5 critical and 78 high, with no Medium or Low fixes listed at all. The previous Chrome version got the same treatment: Chrome 156’s security update fixed 52 flaws, including four critical bugs.
Three Chrome 157 security releases in eight days. But this one is the easiest call of the three: Google has not reported active exploitation of any of the 83, just 83 reasons to restart your browser.
How to update Chrome now
Fixes do not take effect until you relaunch Chrome. These are the steps from CybersecurityNews.
- Open Chrome’s menu, go to Help, then click About Google Chrome.
- Let the update download on the About page.
- Relaunch Chrome so the new version loads.
After relaunching, the same About page shows your version. You want 157.0.8103.78 or 157.0.8103.79 on Windows and Mac, and 157.0.8103.78 on Linux.
What Google has not said about this update
Google has not reported any exploitation of these 83 flaws, and its notice describes no working exploits, according to CybersecurityNews and SecurityOnline. That is a statement about what Google knows, not a guarantee that nobody is looking. Google also keeps bug details and links restricted until a majority of users are updated, longer where shared third-party libraries are affected.
Remote code execution is a possible outcome, not a confirmed one. CybersecurityNews raises it in its headline, but Google’s notice does not state it as an established outcome for these five flaws. The NVD description for CVE-2026-126885 says a remote attacker supplying a crafted HTML page could execute code outside the sandbox, as cited by Threadlinqs.
As of 12 November 2026, the NVD records reviewed by Threadlinqs were awaiting analysis and did not list CVSS metrics. And this notice covers desktop only. PiunikaWeb reported an Android rollout, but Google’s desktop notice does not cover Android, so that part is unverified here.
If your browser has been sitting open for days, this is the update to restart for. The Chrome 157 security update is already out and the rollout is underway. Check the About page for the new build, then relaunch, and you have 83 fewer flaws.


