EUVD-2026-50612
GHSA-8hrm-cqg3-jpx9
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver malicious file to Windows host
-
DeliveryVictim opens file in Chrome
-
ExploitTrigger improper privilege handling in Browser process
-
ExecutionEscalate to higher privileges
-
ImpactExecute actions as elevated user
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: 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 a Windows host running Chrome before 151.0.7922.72 and depends on user interaction (CVSS UI:R): the victim must open or process an attacker-supplied malicious file. Limiting factors are the local attack vector (AV:L - no remote network trigger), the required user action, and platform specificity (Windows only; non-Windows Chrome installs are not indicated as affected). The CVSS lists PR:N (no prior privileges required), but the local, file-delivery nature means the attacker still needs a way to place the file and have the user act on it, which constrains real-world exploitation to scenarios with some local foothold or social-engineering delivery. |
| Impact | The CVSS 3.1 vector CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H yields 7.8 (High): local attack vector, low complexity, no privileges required, but user interaction is needed and scope is unchanged, with high impact across C/I/A. This is a plausible but not urgent priority: exploitation requires local access plus a user action (UI:R), which limits mass, remote exploitation. Google's own Chromium severity rating is only Medium, which is somewhat lower than the 7.8 CVSS suggests - a common divergence because Chrome deprioritizes local/UI-gated issues relative to remote drive-by bugs; note this discrepancy when prioritizing. No EPSS score, SSVC decision, KEV entry, or POC is present in the provided data, so there is no evidence of active or automatable exploitation; the realistic risk is opportunistic local escalation rather than widespread attack. Note the vector's PR:N combined with a local, file-based privilege-escalation description is slightly unusual - verify with the vendor whether any prior foothold is truly unnecessary. |
| Exploit ScenarioDerived | An attacker delivers a specially crafted malicious file to a target - for example via a download, email attachment, or shared drive - and induces the user to open or interact with it in the context of Chrome on Windows. Because the browser mishandles the privileged operation, processing the file escalates the attacker's privileges on the local machine. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 30, 2026
Local privilege escalation in Google Chrome on Windows prior to 151.0.7922.72 lets a local attacker gain elevated privileges through a malicious file that the victim opens or that Chrome processes, stemming from an inappropriate implementation in the Browser process. Google rates the Chromium security severity as Medium, while the NVD-style CVSS of 7.8 reflects high confidentiality, integrity, and availability impact once triggered. No public exploit identified at time of analysis and it is not listed in CISA KEV, but the vendor has shipped a fix.
RemediationAI
Vendor-released patch: update Google Chrome to 151.0.7922.72 or later on Windows via the Stable channel; restart the browser to complete the update so the patched binary is loaded (per https://chromereleases.googleblog.com/2026/07/stable-channel-update-for-desktop_0887107924.html). In enterprise fleets, push the update through your management tooling (e.g., group policy / Chrome Browser Cloud Management) and verify the version rather than relying on background auto-update, which may be delayed. Until patched, reduce exposure by restricting users' ability to open or execute untrusted files and by running Chrome under least-privilege user accounts so a successful escalation yields less; because the trigger is a malicious file requiring user interaction, user awareness and blocking untrusted downloads meaningfully lowers risk, though these controls do not fully substitute for the update.
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 affected component is the Browser process of Chromium-based Google Chrome on the Windows platform, per CPE cpe:2.3:a:google:chrome:*. The root cause is classified as CWE-269 (Improper Privilege Management), described as an 'inappropriate implementation in Browser' - meaning a browser-side operation performs a privileged action or trusts a file without adequately enforcing the privilege boundary. Because it is Windows-specific and triggered 'via a malicious file,' the flaw likely involves how the browser handles file paths, downloaded content, or on-disk resources with more trust than warranted, allowing an operation to run at a higher privilege than the local user should control. The Chromium bug is tracked at issues.chromium.org/issues/520468718.
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
Sources disagree (Medium–Critical)AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Local file-based trigger (AV:L) needing the victim to open the file (UI:R); no prior privileges assumed (PR:N) and full local compromise gives high C/I/A.
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: Chrome
Lifecycle Timeline
4DescriptionCVE.org
Inappropriate implementation in Browser in Google Chrome on Windows prior to 151.0.7922.72 allowed a local attacker to perform privilege escalation via a malicious file. (Chromium security severity: Medium)
Executive ViewAI
Google Chrome for Windows contains a local privilege escalation vulnerability (CVE-2026-17863) that allows attackers with local system access to gain administrative privileges. This exposes Windows-based employee endpoints to lateral movement attacks, data exfiltration, and potential compromise of sensitive systems and applications. A vendor patch is available and should be prioritized for immediate deployment.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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.
Related Vulnerabilities in Google Chrome Prior to 151.0.7922.72 Security Flaws
View all 80Same weakness CWE-269 – Improper Privilege Management
View allSame technique Privilege Escalation
View allVendor StatusVendor
SUSE
Severity: Critical| Product | Status |
|---|---|
| SUSE Package Hub 15 SP7 | Fixed |
| openSUSE Leap 16.0 | Fixed |
| SUSE Package Hub 15 SP7 | Affected |
Exploit-DB