Updated 2026-11-15
Short answer: Google promoted Chrome 157 to the Stable channel on 3 November 2026 as 157.0.8103.38 (Linux) and 157.0.8103.38/.39 (Windows and Mac), with 212 security fixes. Two Stable updates followed: 157.0.8103.50 on 9 November, which fixed the exploited zero-day CVE-2026-125350, and 157.0.8103.78 on 11 November, with 83 security fixes, 5 of them rated Critical. As of 15 November the newest Chrome 157 is 157.0.8103.78 on Linux and 157.0.8103.78/.79 on Windows and Mac (Chrome Releases).
| Date (2026) | Version | What it was |
|---|---|---|
| 22 Oct | 157.0.8103.15/.16 | Early Stable, Windows, a small share of users |
| 28 Oct | 157.0.8103.26/.27 | Early Stable, Windows, a small share of users |
| 3 Nov | 157.0.8103.38 (Linux), .38/.39 (Windows, Mac) | Promotion to Stable, 212 security fixes |
| 9 Nov | 157.0.8103.50 (Linux), .50/.51 (Windows, Mac) | 9 security fixes, including the exploited CVE-2026-125350 |
| 11 Nov | 157.0.8103.78 (Linux), .78/.79 (Windows, Mac) | 83 security fixes |
| 11 Nov | 157.0.8103.78 (Android) | Same security fixes as the desktop release |
Each Stable update rolls out "over the coming days/weeks", so two machines can sit on different builds for a while (Chrome Releases). Extended Stable stays on Chrome 156: 156.0.8078.100 on 11 November with 72 security fixes. Chrome 158 started Early Stable on Windows on 12 November as 158.0.8127.36/.37.
One. For the 9 November update Google wrote: "Google is aware that an exploit for CVE-2026-125350 exists in the wild." CISA added it to its exploited list on 10 November. The 3 and 11 November posts carry no such statement, and no other Chrome 157 CVE is in CISA's catalog of 13 November. The details of the zero-day are in Chrome zero-day CVE-2026-125350.
| CVE | Bug | Effect (NVD) |
|---|---|---|
| CVE-2026-126885 | Use after free in ServiceWorker | Code outside the sandbox via a crafted HTML page |
| CVE-2026-126895 | Use after free in CSS | Code inside the sandbox |
| CVE-2026-126879 | Use after free in Layout | Code inside the sandbox |
| CVE-2026-126846 | Use after free in Skia | Code outside the sandbox, Chrome on Android |
| CVE-2026-126911 | Use after free in Accessibility | Code inside the sandbox |
The other 78 fixes in that update are rated High, for example CVE-2026-126877 in Dawn and CVE-2026-126903 in ANGLE.
chrome://version. It shows the version without starting an update. chrome://settings/help shows it too, but also downloads a pending update.google-chrome --version # Linux defaults read "/Applications/Google Chrome.app/Contents/Info" CFBundleShortVersionString # macOS (Get-Item "$env:ProgramFiles\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion # Windows PowerShell
157.0.8103.78 or higher has every Chrome 157 fix listed here. 157.0.8103.50 has the zero-day fix but not the 83 from 11 November. A running browser keeps the old code until it is relaunched.
FixLane's summary of the 11 November releases: Chrome 157 and Firefox 160 security updates.
Google promoted Chrome 157 to the Stable channel on 3 November 2026, version 157.0.8103.38 on Linux and 157.0.8103.38/.39 on Windows and Mac. Early Stable builds reached a small share of Windows users from 22 October.
157.0.8103.78 on Linux and 157.0.8103.78/.79 on Windows and Mac, released on 11 November 2026 with 83 security fixes. Android got 157.0.8103.78 the same day.
Yes. 157.0.8103.50, released on 9 November 2026, fixes CVE-2026-125350, which Google says is exploited in the wild. Every later Chrome 157 build includes that fix.
Google's posts list 212 at the Stable promotion on 3 November, 9 on 9 November and 83 on 11 November 2026.
Connect an AI agent to the free, read-only FixLane MCP server or ask the Telegram bot: it checks what you have installed against verified fixed versions and serves a reviewed fix procedure. All guides.