EUVD-2026-35245
GHSA-x2hh-w9mw-3vq2
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessVictim loads attacker-controlled page
-
DeliveryMalicious JavaScript delivered to V8
-
ExploitTrigger out-of-bounds read/write in V8
-
ExecutionBuild read/write primitive in renderer heap
-
PersistExecute arbitrary code inside renderer sandbox
-
ImpactExfiltrate in-process data or stage sandbox escape
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Victim must use Google Chrome at a version prior to 149.0.7827.103 and load attacker-controlled HTML/JavaScript in the browser (UI:R - user interaction required, typically a single page visit). No authentication to Chrome or any service is required (PR:N) and no special enterprise configuration is needed - the default JavaScript-enabled, V8-optimized configuration is exploitable. Exploitation is limited by the Chrome renderer sandbox (S:U, scope unchanged): code execution is contained inside the sandboxed renderer process unless chained with a separate sandbox-escape vulnerability, and Site Isolation further restricts cross-origin reach. |
| Impact | Signals point to a real but conditional risk: the CVSS 8.8 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) confirms network-reachable, unauthenticated exploitation requiring user interaction (visiting a page), with scope unchanged because code execution remains inside the sandboxed renderer. Chromium rates the severity High and the patch is shipped through the standard Stable channel update. No EPSS score and no SSVC decision were provided, the CVE is not listed in CISA KEV, and no public POC is referenced - so this is currently a high-impact but not-yet-weaponized issue. Note a data gap: V8 OOB read/write bugs are frequently chained with a sandbox escape in real exploitation, but no such chained CVE is referenced here, so impact assessments should treat sandbox containment as intact unless additional vulnerabilities are disclosed. |
| Exploit ScenarioDerived | An attacker hosts or compromises a website containing crafted JavaScript that triggers the V8 out-of-bounds read/write; a user browsing with a vulnerable Chrome build visits the page (e.g., via phishing link, malvertising, or watering-hole) and the script gains arbitrary code execution inside the renderer sandbox. Without a separate sandbox escape the attacker is limited to renderer-level capabilities such as cross-origin data theft, credential exfiltration from in-process secrets, and staging further exploits; no public POC is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 09, 2026
Remote code execution in Google Chrome's V8 JavaScript engine prior to 149.0.7827.103 allows a remote attacker to execute arbitrary code inside the renderer sandbox by enticing a victim to visit a crafted HTML page. The flaw is an out-of-bounds read and write (CWE-125) rated High severity by Chromium with a CVSS 8.8, and no public exploit identified at time of analysis, though V8 memory-corruption issues historically attract exploit development.
RemediationAI
Vendor-released patch: Chrome 149.0.7827.103 or later on the Stable channel - update immediately via Chrome's built-in updater or by deploying the latest MSI/PKG/DEB package, and restart the browser to activate the fix as described in the Chrome Releases advisory (https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0153744567.html) and tracking issue https://issues.chromium.org/issues/506689381. Operators of Chromium-based browsers and Electron apps should monitor and apply their downstream rebuilds. As compensating controls until patching completes, enable Chrome's Site Isolation (default on desktop) to keep the OOB primitive confined to a single-site renderer, deploy enterprise policy to block untrusted sites or disable JavaScript on high-risk profiles (trade-off: breaks most modern web apps), and consider enforcing the V8 sandbox / Optimizer disable flags only in tightly scoped kiosk deployments since they materially degrade performance and compatibility.
Affected VersionsENISA
Affected Packages
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 Chromium's JavaScript and WebAssembly engine that performs just-in-time compilation and aggressive type/range optimizations on JavaScript objects. CWE-125 (Out-of-bounds Read) - paired here with an out-of-bounds write - typically arises in V8 when optimizer assumptions about array bounds, element kinds, or typed-array offsets diverge from runtime state, allowing a crafted script to read and write outside the intended buffer. Exploitation of such primitives in V8 commonly yields addrof/fakeobj capabilities that lead to arbitrary code execution within the renderer process, though the Chrome sandbox still contains the attacker absent a separate sandbox escape.
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
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
4DescriptionCVE.org
Out of bounds read and write in V8 in Google Chrome prior to 149.0.7827.103 allowed a remote attacker to execute arbitrary code inside a sandbox via a crafted HTML page. (Chromium security severity: High)
Articles & Coverage 1
Executive ViewAI
Google Chrome versions prior to 149.0.7827.103 contain a remote code execution vulnerability in the V8 JavaScript engine that allows attackers to execute arbitrary code on systems when users visit malicious webpages. This threatens the confidentiality and integrity of systems and data accessed through Chrome, affecting all browser users across the organization without requiring credentials or special user actions beyond normal browsing.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
CISA KEV
EPSS
Vulnrichment
VulDB
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
Related Vulnerabilities in Google Chrome Use-After-Free and Memory Safety Flaws
View all 74Same weakness CWE-125 – Out-of-bounds Read
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| openSUSE Leap 16.0 | Fixed |
| openSUSE Tumbleweed | Fixed |
Exploit-DB