CVE-2026-87491

Google Chromium V8 Out of Bounds Write Vulnerability

Actively exploited (CISA KEV) High 8.8 CVSS 3.1

Description

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)

Description as published by the source, in English.

Key facts

Published: 2026-09-09
Last modified: 2026-09-21
Assigned by: chrome-cve-admin@google.com
CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Scored by: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Fix available: Not registered in the sources

Actively exploited

CISA added this vulnerability to the Known Exploited Vulnerabilities catalogue on 2026-09-09, with a remediation deadline of 2026-09-23 for US federal agencies.

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.

Affected products

Vendor	Product	Versions	Status
Google	Chrome	< 153.0.8010.36	Affected

Weakness type

CWE-787: Out-of-bounds Write
The product writes data past the end, or before the beginning, of the intended buffer.

References

https://chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_080814502… Release Notes, Vendor Advisory
https://issues.chromium.org/issues/543557673 Permissions Required
https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-87491 US Government Resource

Related at Berigo

Articles

New malware puts its next move to a vote among four AI models Same product 2026-09-26
Cisco Talos has analysed CLOSEDQUORUM, a Windows implant that hands the choice of its next action to four commercial AI models. Talos has not confirm…
A backdoor built from ordinary Windows tools keeps taking new documents Same product 2026-09-26
On 21 September 2026 Securonix described a backdoor it calls TASK#STOMP, assembled from Windows Script Host, PowerShell and the Task Scheduler. It se…
New malware looks up its command server in a Polygon smart contract Same product 2026-09-26
Blackpoint has found ChainScript, a Node.js remote access trojan spread through fake installers for Spotify, Zoom and Teams. Rather than trusting the…
A flaw in Chrome's JavaScript engine is already being exploited Same product 2026-09-26
On 3 September 2026 Google released Chrome 152.0.7977.82 with twelve security fixes. One of them, CVE-2026-85046 in V8, has an exploit in the wild ac…

Does this affect you?

A vulnerability matters only if you run the product, in an affected version, somewhere an attacker can reach.

Check your asset list Browse all vulnerabilities

Sources and freshness

CVE

What it is: A reference number naming one specific vulnerability, for example CVE-2024-9474.
What it tells you: Which vulnerability we are talking about, and in which product.
What it does NOT tell you: Nothing about how serious it is, whether anyone is exploiting it, or whether it concerns you.
Why it matters: Without a shared number, vendor, authority and tooling cannot discuss the same flaw.
Used with the others: The number is the key. NVD, KEV and EPSS all describe the same CVE.

NVD CWE CISA KEV EPSS

How to read this together

No single value should be used on its own. A high CVSS score does not mean a vulnerability is being exploited, and a low one does not mean it is harmless. The four sources answer four different questions.

CVE names the specific vulnerability.
NVD adds severity and technical detail about it.
CWE describes the type of mistake behind it.
CISA KEV shows that it is already being exploited.
EPSS estimates how likely exploitation is soon.

The order that decides what is urgent

Do you actually have the product?
Is the version you run affected?
Is it listed in CISA KEV?
Does it have a high EPSS score?
Is the system reachable from the internet or from others?
How important is the system to the business?
Are there compensating controls already in place?

The first two questions are not about the vulnerability at all. They are about you, and they remove most of the list before you start.

A short example

Fix this week

CVSS 6,5 (medium)

In CISA KEV: yes
EPSS: 94 per cent
A firewall facing the internet

Can be scheduled

CVSS 9,8 (critical)

In CISA KEV: no
EPSS: 0,04 per cent
A test server with no internet access

Sorted by CVSS alone, the one on the right comes first. It is the more serious flaw in theory. But the one on the left is being used against real organisations right now, and it sits where an attacker can reach it. That is the one to fix first.

The critical one still has to be fixed. It just does not have to be fixed today.

This product uses the NVD API but is not endorsed or certified by the NVD. CVE and the CVE logo are registered trademarks of The MITRE Corporation; CVE records are used under the CVE Terms of Use. CWE is a trademark of The MITRE Corporation, used per the CWE Terms of Use. KEV data from CISA (CC0). Exploitation probability from EPSS, a FIRST.org project. Open-source package data from OSV and the GitHub Advisory Database (CC-BY 4.0).

Scores and vectors are shown as published by the sources. The ordering of results is Berigo's own editorial assessment, described on the search page, and is not NVD data. An empty result never means a system is safe.