CVE-2026-87491

HIGH(8.8)KEV

Google Chromium V8 Out of Bounds Write Vulnerability

Description

CVE-2026-87491 is a high-severity out-of-bounds write vulnerability in the V8 JavaScript engine of Google Chrome and Chromium-based browsers. Google Chrome prior to version 153.0.8010.36 allows a remote attacker to execute arbitrary code inside the browser sandbox via a crafted HTML page, meaning a victim only has to visit an attacker-controlled or compromised website for the memory-corruption vulnerability to trigger. Although Chromium rates the security severity as Medium and the code execution is confined to the renderer sandbox, CVE-2026-87491 carries a CVSS score of 8.8 and has been added to the CISA Known Exploited Vulnerabilities (KEV) catalog, which confirms real attacks against Chrome users.

KEV Information

Vendor
Google
Product
Chromium V8
Date Added
September 9, 2026
Due Date
September 23, 2026
Required Action
Apply mitigations in accordance with vendor instructions, ensuring compliance with CISA’s BOD 26-04 Prioritizing Security Updates Based on Risk (see URL in Notes) guidance and CISA’s “Forensics Triage Requirements” (see URL in Notes). Follow applicable BOD 26-04 guidance for cloud services or discontinue use of the product if mitigations are unavailable. Stakeholders are responsible for evaluating each asset's internet exposure and ensuring adherence to BOD 26-04 patching guidelines.

CVSS Score

Vector String
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HOpen in Calculator
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
NONE
User Interaction
REQUIRED
Scope
UNCHANGED
Confidentiality Impact
HIGH
Integrity Impact
HIGH
Availability Impact
HIGH
Exploitability Score
2.8
Impact Score
5.9

CWEs

Affected Products

VendorProductVersion
googlechrome< 153.0.8010.36

References

Weakness Type

CWE-787: Out-of-bounds Write

An out-of-bounds write occurs when software writes data to a memory location outside the intended boundaries of a buffer, whether through a buffer overflow, incorrect array indexing or faulty pointer arithmetic. In CVE-2026-87491 a crafted HTML page drives V8's JavaScript execution down a path where a write escapes the bounds of its allocation, corrupting adjacent engine memory in a way the attacker can steer toward arbitrary code execution inside the Chrome sandbox.

Learn more: CWE-787 — Out-of-bounds Write

Impact Analysis

CVE-2026-87491 is remotely exploitable over the network with low attack complexity and no privileges, but it does require user interaction — the victim must load a crafted HTML page, which in practice means visiting a malicious site, opening a compromised page, or rendering attacker-supplied content such as a malvertising frame. Once triggered, the impact is high for confidentiality, integrity and availability within the affected component: arbitrary code execution inside the renderer gives an attacker access to the data the browser process handles, including page content, session material and anything reachable from that renderer. The scope is UNCHANGED, which reflects that execution stays inside the Chrome sandbox; a full host compromise would require chaining this bug with a separate sandbox escape. Rated CVSS 8.8 (High) with an EPSS score of roughly 0.9% (56th percentile), the statistical signal is modest, but CISA's KEV listing confirms this V8 vulnerability is being exploited against real Chrome users and sets a remediation deadline of 23 September 2026.

Exploit Maturity

CISA has confirmed active exploitation of CVE-2026-87491 by adding it to the Known Exploited Vulnerabilities catalog with a 23 September 2026 remediation deadline, so this V8 vulnerability is being used against real Chrome users rather than merely reported by researchers. Google's Chrome release notes disclose the fix, and the associated Chromium issue tracker entry remains access-restricted — the standard practice for bugs under active exploitation, which limits public technical detail but does not slow attackers who already hold a working exploit. The EPSS score of about 0.9% (56th percentile) is a poor indicator for freshly patched browser bugs, since EPSS reflects broad scanning behaviour that does not apply to client-side, user-interaction-driven attacks. Treat any unpatched Chrome install as exposed and prioritise the browser update ahead of the KEV deadline.

Remediation

  1. Follow the CISA KEV required action. Apply mitigations in accordance with Google's instructions, comply with CISA's BOD 26-04 "Prioritizing Security Updates Based on Risk" guidance and the "Forensics Triage Requirements", and discontinue use of the product if mitigations are unavailable. The KEV due date is 23 September 2026.
  2. Update Google Chrome to 153.0.8010.36 or later. All versions below that build are affected; the fix shipped in the Chrome Stable channel desktop update, so verify via chrome://settings/help that browsers have restarted after downloading the update — Chrome applies the patch only on restart.
  3. Push the update through managed deployment rather than relying on users. Use Chrome Browser Cloud Management, group policy or your endpoint management platform to enforce the minimum version and trigger a relaunch, and confirm rollout coverage rather than assuming auto-update completed.
  4. Update other Chromium-based browsers. Because the flaw sits in V8, browsers built on Chromium inherit it and require their vendors' corresponding updates; inventory Edge, Brave, Opera, Electron-based applications and embedded Chromium runtimes in your estate and update them to builds carrying the fixed V8.
  5. Reduce browser attack surface and harden long term by keeping site isolation and the sandbox enabled, restricting or blocking unnecessary browser extensions, deploying ad and script filtering to cut exposure to malvertising delivery, and maintaining a short patch window for browsers specifically — V8 memory-safety bugs are discovered frequently and exploited quickly.

Technical Details

CVE-2026-87491 is an out-of-bounds write (CWE-787) in V8, the JavaScript and WebAssembly engine embedded in Chrome. A crafted HTML page containing attacker-supplied script drives V8 into a state where a write operation is performed without a correct bounds check, placing attacker-influenced data outside the intended allocation and corrupting adjacent engine structures such as object headers, backing stores or pointers. From that corruption an attacker builds the usual chain of read and write primitives that ends in arbitrary code execution within the renderer process. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H captures the conditions precisely: network-reachable via a web page, low complexity, no privileges needed, but user interaction required and scope unchanged because the code runs inside the sandbox. Google's own Chromium severity rating of Medium reflects that sandbox confinement, while the CVSS 8.8 reflects the full compromise of the renderer's data.

Frequently Asked Questions

Is CVE-2026-87491 being actively exploited?

Yes. CISA added CVE-2026-87491 to its Known Exploited Vulnerabilities catalog with a remediation due date of 23 September 2026, confirming exploitation in the wild against Chrome users. The associated Chromium bug report is access-restricted, which is Google's usual handling for vulnerabilities under active attack.

What products are affected by CVE-2026-87491?

Google Chrome is affected in all versions before 153.0.8010.36. Because the flaw is in the V8 engine, other Chromium-based browsers and embedded Chromium runtimes — including Edge, Brave, Opera and Electron applications — are affected until they ship a build containing the fixed V8.

How do I fix CVE-2026-87491?

Update Google Chrome to 153.0.8010.36 or later and relaunch the browser so the update is applied. Enforce the minimum version through managed browser policy rather than relying on user-initiated updates, and update every other Chromium-based browser and Electron application in your estate to a build with the patched V8.

How severe is CVE-2026-87491?

CVE-2026-87491 is rated High with a CVSS 3.1 base score of 8.8. It is network-exploitable with low complexity and no privileges but requires the victim to open a crafted page, and the resulting code execution stays inside the Chrome sandbox — Chromium's own rating is Medium for that reason; confirmed KEV-listed exploitation nonetheless makes it an urgent update.

CVSS Score

8.8
HIGH(8.8)

EPSS Score

EPSS Score3.51%
EPSS Percentile89.4%

Dates

PublishedSeptember 9, 2026
Last ModifiedSeptember 21, 2026
StatusAnalyzed
CVSS Versionv3.1

Need Help With Vulnerability Management?

Our security experts can help you prioritize and remediate vulnerabilities effectively.