Skip to main content

Google Chrome CVE-2026-87491

| EUVDEUVD-2026-74529 HIGH
Out-of-bounds Write (CWE-787)
2026-09-09 Chrome GHSA-8x3p-8g9v-xc7m
8.8
CVSS 3.1 · Vendor: Chrome
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure user to crafted HTML page
  2. Delivery
    Deliver malicious JavaScript to unpatched Chrome
  3. Exploit
    Trigger V8 out-of-bounds write in renderer heap
  4. Execution
    Corrupt V8 object metadata to gain code execution
  5. Persist
    Execute arbitrary code within Chrome renderer sandbox
  6. Impact
    Exfiltrate browser-stored session data

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, write limits
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

The victim must navigate to an attacker-controlled or compromised web page using an unpatched Chrome version prior to 153.0.8010.36 (UI:R). No authentication, elevated privileges, or special server-side configuration are required from the attacker side (PR:N, AC:L). The critical limiting factor is Chrome's renderer sandbox: this vulnerability achieves code execution confined to the sandboxed renderer process, not the host operating system - full OS compromise requires a separate, chained sandbox escape exploit. No non-default browser configuration is required for the base exploit to function; any user visiting the crafted page with an affected Chrome version is susceptible.

Impact

The provided CVSS 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) reflects a high-severity network-reachable flaw requiring only user interaction, but the 'inside the sandbox' qualifier in the description is the most important risk-moderating factor. Chromium's internal severity of 'Medium' - rather than Critical or High - is directly explained by S:U: the sandbox boundary is not escaped, so host OS impact requires a separate chained exploit. C:H/I:H/A:H are assessed against the renderer process itself, which holds browser session data, cookies, and credentials - meaningful but not equivalent to OS-level compromise. No public exploit has been identified, and this CVE is not in the CISA KEV catalog. EPSS data was not supplied in the input. Despite Chrome's ubiquitous global deployment footprint, realistic exploitation impact is bounded by sandbox containment absent a known chain.

Exploit ScenarioDerived

An attacker hosts or injects a crafted HTML page containing malicious JavaScript engineered to trigger the V8 out-of-bounds write. A victim on an unpatched Chrome version visits the page - via phishing link, malvertising, or a compromised website - causing the renderer to execute attacker-controlled code within Chrome's sandbox. From that position the attacker can harvest browser session cookies, saved passwords, and browsing data; achieving full OS-level persistence would require chaining this with a separate sandbox escape vulnerability.

Act Now Prioritize within 24-48h. Why: In CISA KEV with patch available.
Exploited in the wild (CISA KEV) Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 09, 2026

Out-of-bounds write in Chrome's V8 JavaScript engine allows remote attackers to execute arbitrary code within the renderer sandbox by directing a user to a crafted HTML page. All Google Chrome versions prior to 153.0.8010.36 are affected across desktop platforms. Impact is bounded by Chrome's renderer sandbox - an attacker achieves control over the renderer process and can access browser-stored data such as session cookies and saved credentials, but reaching the host OS would require a separately chained sandbox escape exploit. No public exploit identified at time of analysis.

RemediationAI

Vendor-released patch: Chrome 153.0.8010.36. Update Google Chrome to version 153.0.8010.36 or later immediately, as detailed in the Chrome stable channel advisory at chromereleases.googleblog.com/2026/09/stable-channel-update-for-desktop_0808145027.html. Chrome auto-updates by default; administrators managing enterprise deployments should verify installed versions and trigger a forced update cycle via group policy or their endpoint management platform. If immediate patching is operationally blocked, restricting user access to untrusted or unknown web origins via DNS filtering, web proxies, or browser isolation solutions reduces exposure to crafted-page delivery, though these controls add latency and complexity and do not eliminate risk from compromised legitimate sites.

Affected VersionsENISA

Chrome 153.0.8010.36 <153.0.8010.36

Affected Packages

euvd chrome fix: 153.0.8010.36

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

V8 is Google's open-source JavaScript and WebAssembly engine embedded in Chrome and Chromium-based browsers. CWE-787 (out-of-bounds write) in the V8 heap can corrupt internal object metadata, forge type information, or overwrite function pointers - enabling attacker-controlled code execution within the renderer process. This class of bug in JIT-compiled runtimes is particularly dangerous because V8 manages large typed arrays and JIT code buffers whose memory layout can be influenced by crafted JavaScript execution patterns. The affected CPE is cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:* covering all versions prior to 153.0.8010.36. Chromium's own internal severity rating of 'Medium' is consistent with the CVSS S:U (scope unchanged) metric, reflecting that the Chrome renderer sandbox boundary is not crossed by this vulnerability alone.

Know when the next one hits your stack

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Chrome) PRIMARY 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 8.8 HIGH

Network-delivered crafted page (AV:N), passive user visit required (UI:R), no authentication (PR:N), sandbox not escaped (S:U), full renderer process compromise (C:H/I:H/A:H).

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N
SUSE CRITICAL
Red Hat 8.8 HIGH

Primary rating from Vendor (Chrome).

CVSS VectorVendor: Chrome

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

4
Added to CISA KEV
Sep 09, 2026 - 19:34 CISA
Patch available
Sep 09, 2026 - 01:03 EUVD
CVE Published
Sep 09, 2026 - 00:09 cve.org
UNKNOWN (no severity yet)
CVE Published
Sep 09, 2026 - 00:09 cve.org
HIGH 8.8

DescriptionCVE.org

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)

Technical POC Analysis

The NVD description and Google's own fix note identify CVE-2026-87491 only as an "out-of-bounds write in V8" - CWE-787.

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

Google Chrome versions prior to 153.0.8010.36 contain a high-severity vulnerability in the V8 JavaScript engine that allows remote attackers to execute arbitrary code within the browser renderer process through a simple user visit to a malicious webpage. Successful exploitation grants attackers access to browser-stored sensitive data including session cookies and saved credentials, potentially compromising authentication to email, banking, and other critical web applications across your organization. An immediate patch is available and deployment is urgent.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Model

5 threats: Elevation of Privilege, Denial of Service, Information Disclosure and 2 more

6-step attack chain with trust boundaries and controls

Full threat model - attack chain, trust boundaries, controls per stage and evidence - is part of the Pro and Business plans.

Threat Intelligence Overview

Threat Score
4.8/10
Composite threat intelligence
EPSS Score
0.3%
Top 79% exploitable
Prevalence
Ubiquitous
world's most widely deployed desktop browser
Threat Intel
3
1 sources
Exploit
POC
Public exploit code exists
Data Quality
10 sources
Confidence: High

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity HIGH
CISA KEV Yes
Public POC Yes
EPSS 0.3%
Patch available Yes
Active threat Yes
Deciding rule
In CISA KEV with patch available
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

119
Low Medium High Critical
KEV: +50
EPSS: 0
CVSS: +44
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: +5

Attack Technique

A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.

Vendor StatusVendor

SUSE

Severity: Critical
Product Status
SUSE Package Hub 15 SP7 Fixed
openSUSE Leap 16.0 Fixed
openSUSE Tumbleweed Fixed
SUSE Package Hub 15 SP7 Affected

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy