Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain local access to Windows host
-
DeliveryStage malicious file for Updater
-
ExploitTrigger use-after-free with user interaction
-
ExecutionCorrupt privileged Updater execution
-
PersistExecute code at OS level
-
ImpactEscalate to elevated 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 | Exploitation requires local access to the Windows host and the ability to place a malicious file that the privileged Chrome Updater component processes, plus user interaction (CVSS UI:R) to trigger the use-after-free; the vulnerable Updater must be a version prior to 150.0.7871.47. Limiting factors: the attack vector is local (AV:L), not remote, so the attacker must already have a foothold or account on the machine; it is Windows-specific; and SSVC marks it Automatable: no, meaning it is not readily scriptable at scale. No prior application privileges are needed (PR:N), but the required file staging and user interaction meaningfully constrain real-world exploitation to targeted local scenarios. |
| Impact | The signals broadly agree this is a real but not urgent priority. CVSS 3.1 base 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicates local vector with required user interaction but no prior privileges, and full CIA impact - matching SSVC's Technical Impact of 'total'. However SSVC also reports Exploitation: none and Automatable: no, and EPSS is very low at 0.13% (3rd percentile), so widespread or automated exploitation is unlikely. Not in CISA KEV and no POC is known. The main caveat: exploitation requires local access plus placement of a malicious file and user interaction, so the practical bar is meaningfully higher than the 7.8 alone suggests. This is a patch-in-normal-cycle item for most environments, prioritized higher on shared/multi-user Windows hosts where local attackers are a realistic threat. |
| Exploit ScenarioDerived | A local, low-privilege user on a shared Windows workstation plants a specially crafted malicious file and induces the required user interaction, triggering the use-after-free in the privileged Chrome Updater as it processes the file. The corrupted, higher-privileged Updater execution is steered to run attacker-controlled code, elevating from a standard account to OS-level privileges. No public POC is currently known, and the local vector plus required interaction (AV:L/UI:R) keep this a targeted rather than opportunistic technique. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 01, 2026
Local OS-level privilege escalation in Google Chrome on Windows (versions prior to 150.0.7871.47) arises from a use-after-free in the Chrome Updater component, letting a local attacker who can plant a malicious file on the system elevate to higher OS privileges. Google rates the Chromium severity as High and has released a fixed Stable channel build; there is no public exploit identified and it is not listed in CISA KEV. EPSS is low at 0.13% (3rd percentile), consistent with a bug that requires local access and user interaction rather than mass remote exploitation.
RemediationAI
Vendor-released patch: upgrade Google Chrome to 150.0.7871.47 or later on Windows via the Stable channel; the primary fix is to allow Chrome's auto-update to apply the patched build and relaunch the browser to complete installation, or push the update through enterprise management (Google Update policies / MSI). Verify via chrome://settings/help. See the vendor advisory at https://chromereleases.googleblog.com/2026/06/stable-channel-update-for-desktop_0175352312.html. As a compensating control until patched, restrict local/interactive logon and file-write access on shared Windows hosts so untrusted users cannot stage the malicious file the exploit requires, and monitor for unexpected activity by the Google Updater service - trade-off is that this does not remove the flaw and tightening local access can disrupt legitimate shared-workstation use; disabling the Updater entirely would break automatic security updates and is not recommended.
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 flaw is a CWE-416 use-after-free within the Chrome Updater - the auto-update service (Google Update / GoogleUpdater) that on Windows can run with elevated/SYSTEM privileges to install browser updates. A use-after-free occurs when memory is freed but a dangling pointer is subsequently dereferenced, allowing an attacker to control the reused allocation and corrupt program state. Because the Updater operates as a privileged Windows component, corrupting its execution via a malicious file yields OS-level privilege escalation rather than mere browser-sandbox compromise. The single affected CPE, cpe:2.3:a:google:chrome:*:*:*:*:*:*:*:*, is Windows-specific per the description.
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:N/UI:R/S:U/C:H/I:H/A:H
Local vector via a malicious file needing user interaction (AV:L/UI:R) with no prior privileges (PR:N), yielding full OS-level compromise, hence high C/I/A.
Primary rating from Vendor (google).
CVSS VectorVendor: google
Lifecycle Timeline
3DescriptionCVE.org
Use after free in Updater in Google Chrome on Windows prior to 150.0.7871.47 allowed a local attacker to perform OS-level privilege escalation via a malicious file. (Chromium security severity: High)
Executive ViewAI
A privilege escalation vulnerability in Google Chrome for Windows (versions before 150.0.7871.47) could allow an attacker with local system access to gain administrative privileges; however, the low exploitation probability (EPSS 0.13%) and requirement for local file placement make this a manageable risk with prompt patching.
Vendor-released patch: Chrome 150.0.7871.47 or later. No interim mitigations available; patching is the definitive control.
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
Severity: Important| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Tumbleweed | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
EUVD-2026-40530
GHSA-gxhr-cwf9-9hr8
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB