Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticated low-privileged local access
-
DeliveryPlant crafted symbolic link/junction
-
ExploitUser Profile Service follows link during file op
-
ExecutionRedirect privileged write to protected path
-
ImpactGain SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V5 - File Handling Symlink resolution safety
|
| Exploitation Conditions | Requires the attacker to already hold valid low-privileged, authenticated local access to the target Windows system (CVSS PR:L, AV:L) - there is no remote or network vector. Exploitation abuses improper link resolution (CWE-59): the attacker must be able to create a symbolic link, junction, or hardlink in a location the Windows User Profile Service processes, so that a privileged file operation is redirected to an attacker-chosen path. Attack complexity is low (AC:L) and no user interaction is needed (UI:N), meaning no victim action or timing/race prerequisite is called out. Limiting factors: the need for an existing authenticated local foothold, the ability to write links in a service-accessed directory, and the absence of any remote trigger; this is a post-exploitation escalation, not an entry point. Default Windows configurations are affected (no special feature must be enabled per the description). |
| Impact | This is a locally-exploitable elevation-of-privilege flaw (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N) in the Windows User Profile Service, a core OS component. The signals are internally consistent and point to a genuine but not emergency priority. CVSS confirms low attack complexity and only low privileges required (any authenticated local user), with high confidentiality, integrity and availability impact - classic SYSTEM-level EoP. CISA's SSVC framing agrees it is serious-but-not-urgent: Exploitation='none' (no observed exploitation), Automatable='no' (local, requires an existing foothold), Technical Impact='total'. No EPSS score was provided, there is no CISA KEV listing, and no public exploit was supplied in the input, so this is not a drive-by or wormable threat. The realistic use case is a second-stage privilege escalation after an attacker already has code execution as a standard user. Note one data inconsistency to verify: the CVE is tagged 'Information Disclosure', but the description and the C:H/I:H/A:H vector describe privilege elevation, not disclosure - treat the tag as mislabeled. Priority: high for patch management on endpoints and multi-user/terminal-server hosts, but it is not a remote-exploitation emergency. |
| Exploit ScenarioDerived | An attacker who already has low-privileged, authenticated local access to a Windows host (e.g., via phishing, a standard user account, or a prior foothold) plants a crafted symbolic link or junction that the User Profile Service resolves during a privileged file operation. Because the service follows the link without proper validation (CWE-59), the operation is redirected to a protected location, letting the attacker gain SYSTEM privileges. No public exploit was identified at time of analysis, and exploitation requires local access, so this is a post-compromise escalation rather than an initial-access vector. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in the Windows User Profile Service (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) lets an attacker who already holds valid low-privileged local access redirect privileged file operations through attacker-created symbolic links, junctions, or hardlinks, yielding high-integrity file writes that can be leveraged for SYSTEM-level code execution. Affected are all currently supported Windows client and server releases - Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2), and Windows Server 2012, 2012 R2, 2016, 2019, 2022, and 2025, including Server Core installations - and default configurations are vulnerable with no special feature needing to be enabled. Vendor-released patches are available from Microsoft; no public exploit code has been identified at time of analysis and CISA's SSVC assessment rates exploitation as 'none', so priority should track routine monthly patching rather than emergency response.
RemediationAI
Apply the Microsoft cumulative update that brings each installation to or above the fixed build for its release - Windows 10 1607 to 10.0.14393.9612, Windows 10 1809/Server 2019 to 10.0.17763.9376, Windows 10 21H2/22H2 to 10.0.19044.7807, Windows 11 23H2 to 10.0.22631.7652, Windows 11 24H2/Server 2025 to 10.0.26100.9711 and 10.0.26100.33650 respectively, Windows 11 25H2 to 10.0.26200.9711, Windows 11 26H1 to 10.0.28000.3231, Windows 11 26H2 to 10.0.26300.9711, Server 2012 to 6.2.9200.26434, Server 2012 R2 to 6.3.9600.23470, and Server 2022 to 10.0.20348.5761 - following the MSRC update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83659. Because this is a local elevation-of-privilege flaw requiring an existing foothold, patch priority is driven by how many non-administrative interactive sessions your estate tolerates; where patching must be staged, reduce exposure by removing or tightly auditing SeCreateSymbolicLinkPrivilege on standard users (partial mitigation only - junction and mount-point reparse points can still be created without that privilege, so this closes just one link type), by restricting and monitoring local interactive logon and Remote Desktop rights so untrusted accounts cannot reach a profile-loading session, and by deploying file-system auditing or Sysmon rules that alert on reparse-point creation inside C:\Users and on privileged writes to system directories originating from ProfSvc context. Isolating multi-user hosts such as RDS and Citrix session hosts deserves the fastest patch cadence, since multiple low-privileged users share the profile-handling code path that this defect abuses.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 20 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-59, improper link resolution before file access ('link following'), in Windows' User Profile Service - the component that creates, loads, and tears down per-user profile directories and routinely performs file operations while running with SYSTEM privileges. Because the service can be induced to follow a reparse point rather than validating the canonical target path, a local attacker can place a symbolic link, junction, or hardlink at a path the service touches during profile handling (creation, load, copy/merge, temporary-profile cleanup, or deletion) and cause a privileged read/write/ACL operation to be applied to an attacker-chosen destination instead. The CVSS vector AV:L/PR:L/UI:N/S:U confirms this is strictly a post-exploitation elevation-of-privilege primitive requiring an existing authenticated local foothold - there is no remote or network trigger and no user interaction or race/timing precondition is called out (AC:L) - and the C:H/I:H/A:H subscores reflect that a successful redirect of a SYSTEM-context file operation typically yields full system compromise. Note that while creating a symbolic link normally requires SeCreateSymbolicLinkPrivilege, junction/mount-point reparse points can be created without it, so the attack surface is broader than the privilege alone suggests. This is a Windows OS-internal component issue rather than a flaw in a separate library or protocol, and no CPE identifiers were supplied beyond the EUVD build-level ranges.
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:N/S:U/C:H/I:H/A:H
Local-only link-following EoP exploitable by any authenticated low-privileged user (AV:L, PR:L) with no special conditions (AC:L, UI:N), yielding full SYSTEM compromise (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Improper link resolution before file access ('link following') in Windows User Profile Service allows an authorized attacker to elevate privileges locally.
Executive ViewAI
Microsoft's Windows User Profile Service has a high-severity flaw that lets a user with existing low-level access on a machine elevate to SYSTEM-level control, affecting all supported Windows client and server versions in default configurations. No public exploit identified at time of analysis, and patch available per vendor advisory. Leadership should prioritize routine monthly patching because the broad exposure and potential for full system compromise outweigh the need for emergency response.
Apply vendor patch.
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.
EUVD-2026-99938
GHSA-6c25-f983-xjm5
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB