Chrome 157 Stable: update to 157.0.8103.38/.39 for 213 security fixes

If chrome://version still shows Chrome 156, you have a new finish line. On Tuesday, November 3, 2026, Google promoted Chrome 157 to the Stable channel for Windows, Mac, and Linux. The builds to look for are:

• Windows / Mac: 157.0.8103.38 or 157.0.8103.39
• Linux: 157.0.8103.38

This replaces our Chrome 156.0.8078.79 note. Same habit: install, fully quit, relaunch, then prove the version. Updating Edge or Firefox does not update Chrome.

What Google shipped on November 3

Google’s Stable Channel Update for Desktop says Chrome 157 is rolling out over the coming days and weeks, and that the update includes 213 security fixes. Google rates seven of them Critical:

• CVE-2026-121156: Buffer overflow in Dawn (Zhenpeng (Leo) Lin at depthfirst)
• CVE-2026-121229: Memory corruption in ANGLE (@mfx)
• CVE-2026-121246: Use after free in WebGL (Google)
• CVE-2026-121035: Use after free in Prerender (Xinyang Ge (Anthropic), assisted by Claude)
• CVE-2026-121247: Buffer overflow in Dawn (Google)
• CVE-2026-121203: Use after free in Geometry (Xinyang Ge)
• CVE-2026-121126: Use after free in Core (Wenbin Liu)

The rest of the list is a long High / Medium / Low mix across GPU, V8, PDFium, Media, Extensions, and more. You do not need every ID. Two hundred thirteen security fixes, with seven Critical, is enough reason to leave 156 behind.

Google’s note does not say any of these bugs are being exploited in the wild. That does not make waiting smart. Browser memory bugs are the kind that become drive-by risk once someone has a working exploit.

Secondary coverage such as SecurityWeek’s Chrome 157 write-up matches the same build numbers and Critical count. Google’s Chrome Releases post remains the source of truth for the Stable promotion.

How to update and verify on a home PC or Mac

1. Open Google Chrome on the computer you actually browse on.
2. Check for updates:
   • Windows / Linux: Menu (three dots) > Help > About Google Chrome, or open chrome://settings/help.
   • Mac: Chrome menu > About Google Chrome, or open chrome://settings/help.
3. Stay on that page until the download finishes and Chrome offers a relaunch, or until it already shows 157.0.8103.38 or .39 (Linux: .38).
4. Relaunch when prompted. Do not click Later and leave old windows open for hours.
5. If the version still looks old, fully quit Chrome (every window). On Windows, confirm no leftover chrome.exe in Task Manager. On Mac, use Chrome > Quit Google Chrome. Open Chrome again.
6. Type chrome://version in the address bar. You want 157.0.8103.38 or 157.0.8103.39 (Linux: .38), or a newer 157 Stable build if Google has already moved past this one.
7. Repeat on other computers you use, including the laptop that sleeps with Chrome still open and any shared family PC.

If About Chrome does not offer 157 yet, give it a day, then check again. Google rolls these out over days or weeks. Stick with Google’s own updater instead of third-party Chrome installers.

Android and iOS Chrome, separately

The same day, Google’s Chrome for Android Update released Chrome 157 (157.0.8103.38) for Android, arriving on Google Play over the next few days. Google says Android releases contain the same security fixes as the matching desktop builds unless noted otherwise.

Google’s Chrome Stable for iOS Update shipped Chrome Stable 157 (157.0.8103.37) for iOS through the App Store.

On a phone or tablet:

1. Update Chrome from Google Play (Android) or the App Store (iPhone / iPad).
2. Open Chrome once after the update so the new build actually launches.
3. On Android, open Chrome’s menu > Settings > About Chrome to read the version. On iPhone or iPad, check the Chrome listing in the App Store, which shows the installed version’s history.

A desktop update does not patch your phone. A phone update does not patch your PC. Chromebooks update on their own ChromeOS path. Updating the Chrome browser on Windows or Mac does not update ChromeOS.

Edge and other Chromium browsers

Microsoft Edge, Brave, and other Chromium-based browsers ship their own builds. Updating Chrome does not update them. If Edge is your daily browser, watch Microsoft’s Edge security release notes for a 157-based Stable (Edge 157 Stable was scheduled for the week of November 5, 2026 on Microsoft’s release calendar) and confirm with edge://version. Brave users should update Brave and check that it reports Chromium 157.0.8103.38 or newer once Brave ships it.

Do this / don’t do that

Do

• Move to 157.0.8103.38/.39 and confirm with chrome://version.
• Fully quit Chrome after the update so old processes are gone.
• Update Android and iOS Chrome from their stores on their own.
• Update Edge, Firefox, Safari, and Brave separately if you use them.

Don’t

• Do not stay on Chrome 156 and assume last week’s .79/.80 patch was the last word.
• Do not download Chrome installers from third-party download sites.
• Do not ignore the computer that only gets used when someone else in the house opens it. That is often the outdated one.

Bottom line

On November 3, 2026, Google moved Chrome Stable to 157.0.8103.38/.39 (Linux .38) with 213 security fixes, including seven Critical issues (Chrome Releases), and shipped matching 157.0.8103.38 Android and 157.0.8103.37 iOS builds. On your own PC or phone: install, relaunch, and verify the version. Chrome 156 was fine last week. Chrome 157 is the new finish line.

Image: Official Google Chrome homepage social image from google.com/chrome.