Skip to content
Reachability Analysis

CVE-2026-87491: Google Chromium V8, is it exploitable where you run it

Code called: openReached: openControl in front: openExploitation known: yesWalk it through the four questions

What the flaw is

This flaw is an out-of-bounds write in V8, the JavaScript and WebAssembly engine that Chrome and every Chromium-based browser share: the engine writes outside a memory buffer it should stay within. A remote attacker can use it through a crafted HTML page to run code inside the browser's sandbox.

The user needs to load the page, and nothing else (CVSS: network, no privileges, user interaction required). The code runs inside the renderer sandbox, so it does not by itself give control of the machine. Attackers usually chain a flaw like this with a separate sandbox escape. Google has not published details of the chain. Chromium's release note rates the bug Medium, while the CVSS 3.1 score is 8.8 (High), calculated by CISA as an additional scorer in NVD. Google gives no reason for the Medium label.

Are you exposed: each condition and how to check it

Condition for exposureHow to check it on your system
Chrome runs a build below the fixed build in the versions table, or was updated but not relaunchedChrome applies an update only after a relaunch, and the same holds for any other Chromium-based browser or embedded Chromium app whose Chromium is older than its fixed build. Open chrome://version, or Menu > Help > About Google Chrome, which also starts the update. At scale: Windows (Get-Item "$env:ProgramFiles\Google\Chrome\Application\chrome.exe").VersionInfo.ProductVersion; Linux google-chrome --version; macOS /Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version. In Chrome Browser Cloud Management, open the Browsers list and read the version column. A pending update shows a Relaunch button on chrome://settings/help; a device that was never restarted still runs the old build even if the new files are on disk. To close the gap on a fleet, set the relaunch policies listed under the mitigation.
the user can be made to open attacker-controlled content (a link, an ad or a compromised site)Review whether managed browsers let users visit the open web. Web filtering and isolation policies change the odds but do not remove the condition.
another Chromium-based browser (Edge, Brave, Opera and others) is older than the build that carries the fixEdge: Settings > About Microsoft Edge (edge://version); the fixed Edge builds are in the versions table. For other browsers, ask the vendor which release ingests the fix; chrome://version shows the Chromium build, and 153.0.8010.36 is the fixed build on the 153 line.
Embedded Chromium or V8 runs untrusted web content (Electron apps, Chromium Embedded Framework, WebView-based tools)For Electron, read the bundled Chromium with process.versions.chrome in the app console. Electron publishes no fixed version for this CVE. As of 19 Nov 2026 Electron's releases data lists no release that bundles Chromium 153; the newest, 44.11.5 (18 Nov 2026), bundles 152.0.7977.169, and neither Google nor Electron says that build carries the fix. So an Electron app has no confirmed fixed version: ask the app's vendor which release does, and until then keep the app away from untrusted pages (load only your own content, open external links in the default browser). An app that bundles Chromium 153.0.8010.36 or later is fixed. Chrome for Android 153.0.8010.36 carries the same security fixes as the desktop release, according to Google's release note of 8 Sep 2026. That note does not mention Android WebView, so check the WebView version separately on devices that use it.

Affected and fixed versions

NVD gives the Chrome range as below 153.0.8010.36. Google's 3 Sep 2026 Stable post (152.0.7977.82/.83) and its 9 Sep 2026 Extended Stable post (152.0.7977.120) do not list this CVE; only the 8 Sep 2026 post for Chrome 153 does. Microsoft's Edge release notes of 4 Sep 2026 say Edge 152.0.4191.66 contains a fix for this CVE; Edge 153.0.4234.32 followed on 10 Sep 2026.
ProductAffected buildsFirst fixed build
Google Chrome, LinuxEarlier than 153.0.8010.36153.0.8010.36
Google Chrome, Windows and MacEarlier than 153.0.8010.36/.37153.0.8010.36/.37
Google Chrome for AndroidEarlier than 153.0.8010.36153.0.8010.36 (same fixes as desktop)
Google Chrome 152 (Stable 152.0.7977.82/.83, Extended Stable 152.0.7977.120)Google names no 152 build with the fixMove to 153.0.8010.36 or later
Microsoft Edge (Chromium-based)Builds before the Microsoft fix152.0.4191.66 (4 Sep 2026) on the 152 line, or 153.0.4234.32 (10 Sep 2026) and later

If the fix cannot go in yet

  • Where users defer updates, enforce a relaunch deadline with Chrome policy: set RelaunchNotification to 2 (required) and RelaunchNotificationPeriod to the number of milliseconds users get before Chrome relaunches itself (the default is 604800000, 7 days; 3600000 is 1 hour). Cost: users lose the option to defer, and open tabs reload on the forced relaunch.
  • Google lists no workaround or settings change for this flaw. Until the update lands, CISA's KEV action is to apply the vendor's mitigations, or stop using the product if none exist. Limiting exposure to untrusted sites for unpatched browsers (web filtering, isolation) reduces risk but is our suggestion, not Google's. Cost: blocked sites.

What to look for

  • Google, Microsoft and CISA publish no indicators of compromise, log strings or file paths for this flaw, and the Chromium issue tracker holds no public detail. The vendor guidance is to update.
  • Endpoint inventory (Intune, Jamf, Chrome Browser Cloud Management or similar) can list browsers below the fixed version so you can force an update and relaunch.

Exploited on the day of disclosure, 4 Sep 2026.

Exploitation reported so far

Microsoft's Edge note of 4 Sep 2026, the first public mention of the CVE, already says the Chromium team reported an exploit in the wild. Google's own note followed on 8 Sep 2026. Neither vendor names an actor, target or date of first use.

Why agent investigation settles it

Exposure is per endpoint: the browser build, whether it was relaunched, and which other Chromium-based apps are installed. An agent or endpoint tool that reads those on each machine settles it, while network reachability tells you nothing because the attacker comes through the user's browser. KEV tells you to treat every unpatched endpoint as a target.

Sources

  1. CVE-2026-87491: NVD record, read 19 Nov 2026
  2. CVE-2026-87491: CISA KEV entry (feed version 2026.11.18), read 19 Nov 2026
  3. CVE-2026-87491: vendor release note (Chrome Releases, Stable Channel Update for Desktop, 8 Sep 2026) advisory, read 19 Nov 2026
  4. CVE-2026-87491: Chrome Releases blog feed copy of the same post, read 19 Nov 2026
  5. CVE-2026-87491: Chrome Releases, Stable Channel Update for Desktop, 3 Sep 2026 (152.0.7977.82/.83), read 19 Nov 2026
  6. CVE-2026-87491: Microsoft Security Update Guide record (Edge fixed build), read 19 Nov 2026
  7. CVE-2026-87491: Microsoft Edge security release notes, read 19 Nov 2026
  8. CVE-2026-87491: Electron releases data (bundled Chromium per release), read 19 Nov 2026
  9. CVE-2026-87491: Chrome Releases, Chrome for Android Update, 8 Sep 2026 (153.0.8010.36), read 19 Nov 2026
  10. CVE-2026-87491: Chrome Releases, Extended Stable Update for Desktop, 9 Sep 2026 (152.0.7977.120), read 19 Nov 2026

Last reviewed 19 Nov 2026.