Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain low-priv local foothold on Windows
-
DeliveryStage malicious file for updater
-
ExploitTrigger Chrome Updater to process file
-
ExecutionExploit use-after-free in updater process
-
PersistHijack execution in privileged context
-
ImpactEscalate to SYSTEM-level privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
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 | Local code execution on a Windows host running a vulnerable Chrome version (below 149.0.7827.53) is required, plus the ability to stage a malicious file consumed by the Chrome Updater component, plus user interaction (UI:R in CVSS) such as triggering an update event or restarting Chrome to invoke the updater. Exploitation is limited to the Windows platform - macOS and Linux Chrome are not affected - and requires the attacker to already hold a low-privileged local account (PR:L), so this is a post-compromise privilege-escalation primitive rather than an initial-access vector. Not exploitable remotely over the network and not exploitable against fully patched endpoints with the auto-updater already cycled to 149.0.7827.53 or later. |
| Impact | The CVSS vector (AV:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H) describes a local attack requiring low privileges and user interaction, yielding high impact across confidentiality, integrity, and availability - consistent with a privilege escalation primitive rather than remote compromise. EPSS at 0.01% (1st percentile) and absence of CISA KEV listing indicate no observed in-the-wild exploitation, and no public exploit identified at time of analysis further reduces immediate risk. However, this class of bug is highly valuable for post-compromise escalation in targeted attacks and for chaining with browser sandbox escapes or initial-access malware, so it warrants timely patching on Windows endpoints despite the low EPSS score. Chromium-rated Medium severity aligns with this assessment of moderate but real risk; the discrepancy between CVSS 7.3 and EPSS 0.01% is typical for local-only Chrome bugs where attackers already need a foothold. |
| Exploit ScenarioDerived | A local attacker with standard user access on a Windows endpoint places a malicious file in a location processed by the Chrome Updater, then triggers the updater to consume it (for example by invoking an update check or restarting Chrome). The use-after-free in the Updater corrupts memory in the privileged updater process, granting the attacker OS-level code execution to escalate from user to SYSTEM. No public exploit identified at time of analysis, but the bug class is well-understood and attractive for post-exploitation tooling. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 06, 2026
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.
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.
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
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.
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:L/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.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)
Executive ViewAI
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. Organizations managing shared workstations, development machines, or systems where file placement may be accessible to low-privileged users face direct risk of endpoint security compromise. Immediate deployment of Chrome 149.0.7827.53 or later is required to eliminate this privilege escalation vector.
Vendor-released patch: Chrome 149.0.7827.53 or later. Apply immediately.
Threat Intelligence Overview
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
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.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
Same weakness CWE-416 – Use After Free
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
| Product | Status |
|---|---|
| openSUSE Tumbleweed | Fixed |
EUVD-2026-34576
GHSA-3wpf-w9w2-6m84
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB