---
title: Tip: after a Chrome zero-day, check what version is actually running, not what's installed | ctxsec
url: https://ctxsec.com/items/tip-confirm-chrome-157-0-8103-50-fleetwide-after-zero-day
description: "Chrome downloads updates in the background but only applies them on relaunch, so endpoints can report the new version on disk while still running the vulnerable one. For CVE-2026-125350 the target is 157.0.8103.50 or later on Stable and 156.0.8078.96 on Extended Stable."
status: "operational guidance (version numbers from the Chrome Releases blog, Nov 9, 2026)"
published: 2026-11-09
---

> Chrome downloads updates in the background but only applies them on relaunch, so endpoints can report the new version on disk while still running the vulnerable one. For CVE-2026-125350 the target is 157.0.8103.50 or later on Stable and 156.0.8078.96 on Extended Stable.

[← Tips & Guides](/tips) · [markdown](/items/tip-confirm-chrome-157-0-8103-50-fleetwide-after-zero-day.md)

operational guidance (version numbers from the Chrome Releases blog, Nov 9, 2026)

2026-11-09

### Tip: after a Chrome zero-day, check what version is actually running, not what's installed

- **Managed fleets:** use the Chrome browser cloud management or your EDR's software inventory to list running versions, and set the RelaunchNotification and RelaunchNotificationPeriod policies to force a restart within hours.
- **Spot check:** `chrome://version` or `chrome://settings/help` shows the running build.
- **Don't forget** Chromium-based browsers and desktop apps that embed their own Chromium; they patch on their vendor's schedule.

Sources: [Chrome Releases: Stable Channel Update for Desktop (Nov 9, 2026)](https://chromereleases.googleblog.com/2026/11/stable-channel-update-for-desktop_018223192.html) · [Chrome Releases: Extended Stable Update for Desktop (Nov 9, 2026)](https://chromereleases.googleblog.com/2026/11/extended-stable-update-for-desktop_0910980127.html)