What is the CVSS score of EUVD-2026-35245?

EUVD-2026-35245 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Google Chrome are affected by EUVD-2026-35245?

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…. A patch is available.

Is there a public PoC exploit available for EUVD-2026-35245?

Yes, a public proof-of-concept exploit is available for EUVD-2026-35245. Prioritise patching immediately. EPSS: 0.1%.

How to fix or mitigate EUVD-2026-35245?

24 hours: Identify Chrome deployment scope and inventory across endpoints. 7 days: Deploy Chrome 149.0.7827.103 or later to all systems; prioritize endpoints with access to business-critical applications. 30 days: Verify complete deployment across the organization and establish monitoring for exploitation indicators.

Google Chrome EUVD-2026-35245

| CVE-2026-11645 HIGH

Out-of-bounds Read (CWE-125)

2026-06-09 chrome-cve-admin@google.com

GHSA-x2hh-w9mw-3vq2

Information Disclosure Google Buffer Overflow RCE

8.8

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

8.8 HIGH

AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

SUSE

CRITICAL

qualitative

Red Hat

9.6 HIGH

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Added to CISA KEV

Jun 09, 2026 - 17:32 CISA

Analysis Generated

Jun 09, 2026 - 02:49 vuln.today

CVSS changed

Jun 09, 2026 - 02:22 NVD

8.8 (HIGH)

CVE Published

Jun 09, 2026 - 00:16 nvd

UNKNOWN (no severity yet)

CVE Published

Jun 09, 2026 - 00:16 nvd

HIGH 8.8

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

POC CVE-2026-11645: Chrome V8 Out-of-Bounds Read/Write RCE, CVSS 8.8, Active Exploitation Jun 10, 2026

AnalysisAI

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.

Technical ContextAI

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.

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.