Skip to content
Fencer Vulns
high 8.8

CVE-2026-87491 kev in the critical feed json

Out of bounds write in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox vi…

published 2026-09-09 2 mo ago modified 2026-09-21 48 d ago also EUVD-2026-74529

cvss
8.8
version 3.1, CNA
cisa kev
Exploited
added 2026-09-09
epss
3.5%
EPSS 3.5% chance of exploitation in 30 days, percentile 89%
public exploits
0
none known

Summary

Out of bounds write in V8 in Google Chrome prior to 153.0.8010.36 allowed a remote attacker to execute arbitrary code inside the sandbox via a crafted HTML page. (Chromium security severity: Medium)

Patch / fix

cisa 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.

  • google chrome 153.0.8010.36
  • chromium Debian 12 153.0.8010.52-1~deb12u1
  • chromium Debian 13 153.0.8010.47-2~deb13u1
  • chromium Debian 14 153.0.8010.47-1

debian advisories DEBIAN-CVE-2026-87491

  • chromium openSUSE Leap 16.0 153.0.8010.52-bp160.1.1
  • chromium openSUSE Tumbleweed 153.0.8010.36-1.1

opensuse advisories openSUSE-SU-2026:21921-1openSUSE-SU-2026:11750-1

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2026-87491 updated cvss 8.8

chromium-browser: chromium-browser: Out of bounds write in V8

  • Red Hat All currently supported Red Hat products
    not affected: vulnerable code not present

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Timeline

  1. 0-day patched (Project Zero)
  2. Added to CISA KEV
  3. Published
  4. CISA SSVC: exploitation active
  5. CISA patch deadline

Known exploited

Added
2 mo ago
Patch by
2026-09-23 (47 d ago)
Ransomware
Not known
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.
Vendor, product
Google, Chromium V8
CISA name
Google Chromium V8 Out of Bounds Write Vulnerability

Zero-day

Detected in real attacks while still unknown to the vendor and the public, per Google Project Zero's 0day In-the-Wild tracker.

Patched
2026-09-08
Details
project zero tracker

CISA SSVC

Exploitation
Active, exploited in the wild
Automatable
no
Technical impact
total
Assessed
1 mo ago

Exploit prediction

3.51% chance of exploitation in the next 30 days, higher than 89% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
CISA ADP 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
CNA 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

  • Google Chrome

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.