Skip to content
Zero Day Playbook

The endpoint fleet playbook for the first 72 hours

  • 0 to 4 hours: 4 steps
  • 4 to 24 hours: 2 steps
  • 24 to 72 hours: 2 steps
  • Hours elapsed: the bar under the cells

Checklist to print

  1. 0 to 4 hours4 steps, due by hour 4
    1. 1

      Security lead, hand-off

      Write the fixed-build list, one line per browser family. Chrome: 153.0.8010.36 on Linux, 153.0.8010.36 or .37 on Windows and Mac, 153.0.8010.36 on Android. Edge: Microsoft's Security Update Guide ties the CVE to Edge 152.0.4191.66 (Chromium 152.0.7977.83), and Edge 153.0.4234.32 and later builds on the 153 line carry it. Other Chromium browsers: open chrome://version and compare the Chromium version to 153.0.8010.36.

      Done at

    2. 2

      Platform engineering, hand-off

      Find machines that have the new files but still run the old code. Run this as SYSTEM so it sees every user's processes: foreach ($r in "$env:ProgramFiles\Google\Chrome\Application", "${env:ProgramFiles(x86)}\Google\Chrome\Application", "$env:LOCALAPPDATA\Google\Chrome\Application") { if (Test-Path $r) { $new = Get-ChildItem $r -Directory | Where-Object Name -match '^\d+\.\d+\.\d+\.\d+$' | Sort-Object { [version]$_.Name } | Select-Object -Last 1; $old = Get-Process chrome -ErrorAction SilentlyContinue | Where-Object { $_.Path -like "$r*" -and $_.StartTime -lt $new.CreationTime }; [pscustomobject]@{Host=$env:COMPUTERNAME; Installed=$new.Name; StaleProcesses=@($old).Count} } }. A process that started before the newest version folder was created is still running the previous build. A single machine shows the same state at chrome://settings/help as a Relaunch button. For installed versions only, use (Get-Item "$env:ProgramFiles\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion, google-chrome --version on Linux, or the Browsers list in Chrome Browser Cloud Management. For installed Edge versions use (Get-Item "${env:ProgramFiles(x86)}\Microsoft\Edge\Application\msedge.exe").VersionInfo.ProductVersion on Windows, microsoft-edge --version on Linux, or edge://version on one machine.

      Done at

    3. 3

      Platform engineering, hand-off

      Set the Chrome relaunch policies. RelaunchNotification = 2 (Required) and RelaunchNotificationPeriod = 14400000 (4 hours, in milliseconds). On Windows set both as REG_DWORD under HKLM\SOFTWARE\Policies\Google\Chrome; on Linux put {"RelaunchNotification": 2, "RelaunchNotificationPeriod": 14400000} in a file in /etc/opt/chrome/policies/managed/; on macOS set the same keys for com.google.Chrome; in Chrome Browser Cloud Management set the same policies in the console. Google's policy text: "If set to 'Required', a recurring warning will be shown to the user indicating that a browser relaunch will be forced once the notification period passes." The default period is one week (604800000) and the minimum is one hour (3600000). With 4 hours, the app menu changes at 1 hour 20 minutes, changes color at 2 hours 40 minutes, and the relaunch is forced at 4 hours. Leave RelaunchWindow unset: Google warns that "Setting this policy may delay application of software updates."

      Done at

    4. 4

      Platform engineering, hand-off

      Set the same relaunch policies for Edge, which has the same names. Windows: REG_DWORD values RelaunchNotification = 2 and RelaunchNotificationPeriod = 14400000 (0x00DBBA00) under HKLM\SOFTWARE\Policies\Microsoft\Edge, or Group Policy path Administrative Templates/Microsoft Edge/Relaunch with the MSEdge.admx template. macOS uses the same key names. Microsoft: "If you set the policy to 'Required', a recurring warning prompts users that the browser will be restarted automatically as soon as a notification period passes." Edge refreshes the policy dynamically, so a running browser picks it up. Also set RelaunchFastIfOutdated to 7 (Chrome 137 and later, Edge 141 and later): when the running version has been outdated for more than that many days, the notification period drops to 2 hours. Both vendors' text for that policy calls Required "1" although the RelaunchNotification table says Required is 2, so set RelaunchNotification to 2.

      Done at

  2. 4 to 24 hours2 steps, due by hour 24
    1. 5

      Platform engineering, hand-off

      Do not wait for the staged rollout. Push the current stable installer through your software tool: the Chrome Enterprise MSI on Windows, the package on macOS, and apt-get install --only-upgrade google-chrome-stable or dnf upgrade google-chrome-stable on Linux. For Edge, run the same push of the current Edge installer. A user can also start the update at Menu > Help > About Google Chrome. Then rerun the stale-process check from the second step.

      Done at

    2. 6

      Platform engineering, hand-off

      Find Chromium that no browser update touches. On Windows run Get-ChildItem 'C:\Program Files','C:\Program Files (x86)',$env:LOCALAPPDATA -Recurse -Include libcef.dll,chrome_100_percent.pak -ErrorAction SilentlyContinue | Select-Object -ExpandProperty DirectoryName -Unique. libcef.dll marks Chromium Embedded Framework applications and chrome_100_percent.pak marks Electron and Chromium builds. For an Electron app, read process.versions.chrome in the app's console. Then ask each app's vendor which release includes Chromium 153.0.8010.36 or later. Chrome for Android WebView follows the Chrome for Android update to 153.0.8010.36.

      Done at

  3. 24 to 72 hours2 steps, due by hour 72
    1. 7

      Platform engineering, hand-off

      Block laptops that stay off the network until they update. In Intune create a custom compliance policy for Windows with a discovery script that prints {"ChromeCurrent": true} or false from $v = (Get-Item "$env:ProgramFiles\Google\Chrome\Application\chrome.exe" -ErrorAction SilentlyContinue).VersionInfo.ProductVersion; ($v -and [version]$v -ge [version]'153.0.8010.36'), and a rule on ChromeCurrent with the operator IsEquals, data type Boolean and operand true. Require a compliant device in Conditional Access for corporate web apps. Add the same pair for Edge, reading msedge.exe from "${env:ProgramFiles(x86)}\Microsoft\Edge\Application". Its floor is 152.0.4191.66 on the 152 line, or 153.0.4234.32 on the 153 line and later (Microsoft's release notes of 4 and 10 Sep 2026); compare each build against the floor of its own line.

      Done at

    2. 8

      Security lead, hand-off

      Report two numbers every 12 hours: the share of machines on a fixed installed version, and the share with no stale process. Stop at the second. Then close: list every exception, whether a machine, an embedded app or a vendor without a date, with an owner and a date, and give the people exposed on an old build after 8 Sep the same notice as everyone else. Google, Microsoft and CISA publish no indicators of compromise for this flaw and the KEV entry marks forensicTriage No, so there is no hunt to run; the record of who ran old code, and when, is the evidence.

      Done at

A browser fix is two events, not one: the new files arrive, and the running process restarts. Chrome applies an update only after a relaunch, and a person who keeps forty tabs open can postpone that for weeks. CVE-2026-87491 is an out-of-bounds write in V8, Chrome's JavaScript engine. The attacker needs only a crafted page, so a link, an ad or a compromised site is enough (CVSS vector AV:N, UI:R). The code runs inside the renderer sandbox, so reaching the machine usually takes a second flaw. Chromium rated the bug Medium, while CVSS 3.1 gives it 8.8; the Medium label did not stop Google from stating that an exploit exists in the wild.

Nothing in the operating system patch tool owns this. Each Chromium browser takes the fix on its own schedule: Microsoft shipped Edge 152.0.4191.66 on 4 Sep 2026, four days before Chrome 153 reached the stable channel, and Google said Chrome 153 would "roll out over the coming days/weeks". Apps that embed Chromium, such as Electron and CEF applications, wait for their own vendors. Laptops sit off the network for days. The steps below cover what only an endpoint fleet has: versions that differ by vendor, a relaunch that users defer, and bundled runtimes.

When no fix exists yet

Google lists no workaround or settings change for this flaw, and CISA's required action is to apply the vendor's mitigations or stop using the product. For a Chromium build with no fix yet, such as an embedded browser whose vendor gives no date, there are two controls and both are our suggestion, not Google's. First, restrict what the app can open: if it renders only your own pages, the attacker has no route to it; if it opens any URL, add a URLBlocklist or an allow list. The cost is blocked sites. Second, turn off the JavaScript JIT: DefaultJavaScriptJitSetting = 2 in Chrome, and the same policy exists for Edge. Google says this "may render web content more slowly, and may also disable parts of JavaScript including WebAssembly", and it helps only if this flaw sits in the JIT compiler, which Google has not said. Treat it as a stopgap for people who face untrusted pages all day.

Take an application out of use when it renders pages from the open web, its vendor has no fixed build and no date, and people cannot work without a different route. Leave it running when it shows only first-party content and its vendor has given a date inside the KEV window of 14 days. Remember the sandbox: the code runs inside the renderer, so an unpatched browser alone does not hand over the machine, and the real escalation needs a second flaw that no source ties to this one.

CVE-2026-87491 worked through, day by day

Google's Chrome 153 release note of 8 Sep 2026 listed 230 security fixes. One was CVE-2026-87491, an out-of-bounds write in V8 that Google rated Medium and described as having an exploit in the wild. Microsoft's Edge notes show the fix arriving earlier in Edge than in Chrome's public note, and CISA listed the CVE the day after Chrome 153 went out. The sources give dates, and hours only for the Microsoft record, so the table runs in days.

WhenWhat happenedSource
6 Aug 2026Jihyeon Jeong of Compsec Lab, Seoul National University reports the bug as Chromium issue 543557673. Google pays $2,500.source
4 Sep 2026Microsoft releases Edge 152.0.4191.66. Its release note says "The Chromium team reported that CVE-2026-87491 has an exploit in the wild, and this update contains a fix for it."source
8 Sep 2026Chrome 153.0.8010.36 (Linux) and 153.0.8010.36/.37 (Windows, Mac) reach the stable channel. The note says the release "will roll out over the coming days/weeks" and that Google is aware an exploit for CVE-2026-87491 exists in the wild. The bug is listed as Medium.source
9 Sep 2026CISA adds CVE-2026-87491 to KEV with forensicTriage No and a due date of 23 Sep 2026. The entry says it could affect Chrome, Edge and Opera.source
10 Sep 2026Microsoft releases Edge 153.0.4234.32 for Stable.source
11 Sep 2026, 21:56 (UTC minus 7)Microsoft's Security Update Guide record for the CVE is released. It says Edge "ingests Chromium" and repeats that Google is aware of an exploit in the wild.source
23 Sep 2026KEV due date for CVE-2026-87491: 14 days after the CISA listing of 9 Sep and 15 days after the Chrome note of 8 Sep.source

On the default policy, a laptop that stages the update on day 3 (11 Sep) is forced to relaunch on day 10 (18 Sep), 168 hours later and 5 days before the KEV due date. A laptop that stages it on day 12 passes the due date before the timer ends. With RelaunchNotificationPeriod at 14400000, the relaunch is forced 4 hours after the update stages. The push in the fifth step moves staging from days or weeks to hours 4 to 24 for machines on the network, so the fleet finishes online machines by about hour 28 and spends the remaining time on laptops and bundled apps. An Edge fleet that took the 4 Sep build had the fix 4 days before Google's note existed.

Sources

  1. Chrome Releases, Stable Channel Update for Desktop, 8 Sep 2026, read 19 Nov 2026
  2. Chrome Enterprise policy list data (RelaunchNotification, RelaunchNotificationPeriod, RelaunchWindow, RelaunchFastIfOutdated, DefaultJavaScriptJitSetting), read 19 Nov 2026
  3. Microsoft Edge policy documentation, RelaunchNotification, read 19 Nov 2026
  4. Microsoft Edge policy documentation, RelaunchNotificationPeriod, read 19 Nov 2026
  5. Microsoft Edge policy documentation, RelaunchFastIfOutdated, read 19 Nov 2026
  6. Microsoft Edge security release notes, read 19 Nov 2026
  7. Microsoft Security Update Guide record for CVE-2026-87491, read 19 Nov 2026
  8. CISA Known Exploited Vulnerabilities feed, catalog version 2026.11.18, read 19 Nov 2026

Last reviewed 19 Nov 2026.