Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local account
-
ExploitLaunch crafted Windows Installer operation
-
ExecutionTrigger use-after-free and win reclaim race
-
ImpactExecute code as SYSTEM
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 | Requires the attacker to already hold a low-privileged authenticated local account on the target Windows system (PR:L, AV:L) - there is no remote or unauthenticated path. Exploitation specifically abuses the Windows Installer (MSI) service to trigger a use-after-free, and the high attack complexity (AC:H) means success depends on reliably winning a memory-reuse timing race, which is non-deterministic and limits practical weaponization. Limiting factors: local access prerequisite, existing authentication, and the race-condition reliability barrier; no user interaction (UI:N) is needed once the attacker has local code execution. |
| Impact | Signals point to a credible but non-urgent local privilege-escalation issue rather than a mass-exploitation emergency. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U) confirms the attacker must already have local, authenticated (low-privilege) access AND overcome high attack complexity - characteristic of the race/timing window typical of use-after-free (CWE-416) flaws - which meaningfully dampens the 7.0 base score and total technical impact (C:H/I:H/A:H). CISA's SSVC framework reinforces this: Exploitation=none (no observed exploitation) and Automatable=no, even though Technical Impact=total. There is no CISA KEV listing and no POC referenced in the provided data, so exploitation status is 'no public exploit identified at time of analysis.' EPSS is not provided in the input, so probabilistic exploitation likelihood cannot be quantified here. No signals conflict: local-only vector, high complexity, required privileges, and SSVC 'Exploitation: none' all consistently indicate a real-but-lower-priority patch - important for hardened/multi-user Windows hosts where an authenticated foothold already exists, but not an internet-facing or wormable threat. A vendor patch is available and should be applied on normal Patch Tuesday cadence, prioritized higher on shared/terminal-server systems. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged authenticated account on a Windows host (e.g., via phishing, a prior foothold, or a standard user on a shared/terminal server) runs a crafted program that abuses the Windows Installer service to trigger a use-after-free, winning a timing race to reclaim the freed object and execute code at SYSTEM. No public exploit code is identified at time of analysis, and the high attack complexity (AC:H) means exploitation requires reliably hitting a narrow race window. |
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 Installer service allows an authenticated attacker holding a low-privileged account to corrupt memory via a use-after-free and, if successful, obtain high-integrity code execution on the affected Windows host. The issue is rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N) and affects a broad range of Windows 10, Windows 11, and Windows Server builds up to vendor-published fixed builds; no public exploit code has been identified at time of analysis and CISA's SSVC assessment records exploitation as 'none'. Because exploitation requires existing local access, a valid low-privileged session, and a reliable win in a non-deterministic memory-reuse race (AC:H), this is a credible but non-urgent post-compromise escalation vector rather than a mass-exploitation emergency. Vendor patches are available per the Microsoft advisory.
RemediationAI
Apply the vendor-released Microsoft security update for each affected Windows branch; patching is the primary and recommended fix. Fixed builds per the affected-version data include 10.0.17763.9376 for Windows 10 1809 / Windows Server 2019, 10.0.14393.9612 for Windows 10 1607 / Windows Server 2016, 10.0.19044.7807 for Windows 10 21H2 and 22H2, 10.0.22631.7652 for Windows 11 23H2, 10.0.26100.9711 for Windows 11 24H2, 10.0.26100.33650 for Windows Server 2025, 10.0.20348.5761 for Windows Server 2022, 6.2.9200.26434 for Windows Server 2012, and 6.3.9600.23470 for Windows Server 2012 R2; systems at or above these builds are patched. Because the issue is local-only and requires an existing low-privileged authenticated session (AV:L/PR:L, AC:H), priority should follow exposure: multi-user and RDP-enabled systems, terminal servers, and hosts running untrusted local workloads are the highest-risk candidates for rapid deployment, while single-user endpoints can follow the normal monthly cadence. If immediate patching is not possible, the most effective compensating control is to assume breach of any local account and reduce the local attack surface: restrict interactive and Remote Desktop logon rights to only required users, remove unnecessary local administrator membership and unused local accounts, and enforce least privilege so a foothold cannot be leveraged for escalation. Where the installer is not operationally required (locked-down kiosks, hardened server roles managed by image-based deployment), stopping and disabling the Windows Installer service (msiserver) removes the attack path entirely, at the cost of breaking legitimate software installation, repair, and MSI-based update workflows on that host. Detection and monitoring should focus on MsiInstaller operational events (including 1040/1042 and unexpected transaction rollbacks) correlated with anomalous process creation from msiexec.exe or msiserver, and on unexpected token or integrity-level changes for processes spawned beneath the installer; this visibility is limited, however, because a successful race-condition exploit may leave little distinctive telemetry. Vendor advisory and update details: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83752.
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 vulnerability is a use-after-free (CWE-416) in Windows Installer, the MSI-based service (msiserver) that processes .msi/.msp package installation, repair, rollback, and custom-action execution on Windows hosts. A use-after-free occurs when the installer frees an object - typically a heap allocation tied to package metadata, custom action state, or an installer transaction structure - and later dereferences a stale pointer to that memory; if the attacker can arrange for controlled data to be reallocated into the freed region before the stale dereference, the result is memory corruption that can be steered toward code execution or a system crash (hence the Denial Of Service and Memory Corruption tags alongside Use After Free). Root cause class: improper memory lifetime management in a privileged Windows service that runs installation logic in a higher-integrity context than the invoking user. The assessed CVSS vector CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H confirms the attack surface is local, requires an authenticated low-privileged account (PR:L), needs no user interaction once local code execution is achieved (UI:N), and applies high attack complexity (AC:H) because the high-integrity outcome depends on winning a non-deterministic heap-reuse timing race. Impact is scoped Unchanged but rated High for confidentiality, integrity, and availability, consistent with successful elevation to SYSTEM-level execution; CISA's SSVC rates technical impact as 'total' while noting the attack is not automatable and exploitation has not been observed.
Know when Windows gets its next vulnerability
- 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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only exploitation by an authenticated low-privileged user (AV:L/PR:L), high complexity due to the use-after-free race window (AC:H), yielding full SYSTEM compromise (C:H/I:H/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Installer allows an authorized attacker to elevate privileges locally.
Executive ViewAI
Microsoft Windows 10, Windows 11, and Windows Server are affected by a high-severity local privilege escalation vulnerability (CVE-2026-83752) in the Windows Installer service. An authenticated attacker with a low-privileged account could exploit a use-after-free memory corruption to achieve high-integrity code execution, potentially compromising the entire host. Although no public exploit identified at time of analysis and exploitation requires local access and winning a race condition, organizations should prioritize patching to prevent post-compromise escalation and protect sensitive systems.
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.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
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.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-99979
GHSA-r4pf-rv3r-32vh
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB