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

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

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

Google Chrome on Windows contains a use-after-free vulnerability (CVE-2026-11115) that allows local attackers who can place a malicious file to escalate to operating system-level privileges.. A patch is available.

How to fix or mitigate EUVD-2026-34576?

Within 24 hours: audit Windows endpoints running Chrome versions prior to 149.0.7827.53 and stage deployment of Chrome 149.0.7827.53 or later. Within 7 days: deploy Chrome 149.0.7827.53 or later across all Windows systems, prioritizing shared terminals and multi-user workstations. Within 30 days: verify through automated compliance scanning that 100% of Chrome installations on Windows are version 149.0.7827.53 or later.

Google Chrome EUVD-2026-34576

| CVE-2026-11115 HIGH

Use After Free (CWE-416)

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

GHSA-3wpf-w9w2-6m84

Privilege Escalation Denial Of Service Google Use After Free Memory Corruption Microsoft

7.3

CVSS 3.1 · Vendor: google

Severity by source

Vendor (google) PRIMARY

7.3 HIGH

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

Red Hat

7.3 MEDIUM

qualitative

Primary rating from Vendor (google).

CVSS VectorVendor: google

Attack Vector

Local

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jun 06, 2026 - 05:23 vuln.today

CVSS changed

Jun 06, 2026 - 05:22 NVD

7.3 (HIGH)

CVE Published

Jun 04, 2026 - 23:17 nvd

HIGH 7.3

CVE Published

Jun 04, 2026 - 23:17 nvd

UNKNOWN (no severity yet)

DescriptionCVE.org

Use after free in Updater in Google Chrome on Windows prior to 149.0.7827.53 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: Medium)

AnalysisAI

Local privilege escalation in Google Chrome on Windows prior to 149.0.7827.53 stems from a use-after-free condition in the Updater component, allowing a local attacker who can place a malicious file to elevate to OS-level privileges. The flaw was reported by Google's Chrome security team with no public exploit identified at time of analysis, and EPSS scoring is very low at 0.01% reflecting minimal predicted exploitation activity. Chromium rates the severity as Medium while the CVSS base score of 7.3 reflects the high impact of OS-level privilege escalation.

Technical ContextAI

The vulnerability resides in Chrome's Updater component on Windows, which is the auto-update service responsible for maintaining browser versions and typically operates with elevated privileges to write to protected program directories. CWE-416 (Use After Free) describes a memory safety flaw where memory is referenced after it has been freed, often leading to memory corruption, crashes, or arbitrary code execution depending on heap layout and attacker control over the freed memory region. Because the Chrome Updater runs as a privileged Windows service or scheduled task, a use-after-free triggered by a malicious file processed by the updater provides a path from low-privilege user context to SYSTEM or administrator-level code execution.

RemediationAI

Vendor-released patch: Google Chrome 149.0.7827.53 for Windows - upgrade immediately via the Chrome Releases stable channel update referenced at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop.html, which is delivered automatically by the Chrome Updater on next browser restart. Enterprise administrators using Chrome Browser Cloud Management or group policy should confirm the update has rolled out across fleet endpoints and force-restart browsers if needed. As compensating controls until patching, restrict local users' ability to write files to directories monitored or processed by the Chrome Updater service and apply Windows application control (WDAC or AppLocker) to limit execution of unsigned binaries placed by low-privilege users, with the trade-off of potential disruption to legitimate user-installed tools.