Skip to main content

Windows Installer CVE-2026-85361

| EUVDEUVD-2026-99486 HIGH
Use After Free (CWE-416)
2026-10-13 secure@microsoft.com GHSA-45mj-c79v-cvc8
7.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as low-privileged local user
  2. Delivery
    Trigger use-after-free in Windows Installer
  3. Exploit
    Win race / reclaim freed object
  4. Execution
    Execute code as SYSTEM
  5. Impact
    Full local privilege escalation

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 an attacker to already be authenticated on the target as a local low-privileged user (PR:L) and to have local access (AV:L) - there is no remote or network-facing attack surface. The HIGH attack complexity (AC:H) indicates a meaningful limiting factor: the use-after-free almost certainly must be triggered by winning a race condition or forcing a specific allocation/free timing in the Windows Installer (msiexec) service, so exploitation is not reliable on a single attempt. No user interaction is needed (UI:N) and no non-default configuration is called out - the flaw is in the core Installer component present in all supported Windows editions, so the primary practical limits are the need for prior local access and the timing-dependent reliability of the use-after-free.

Impact

This is a locally-exploitable elevation-of-privilege flaw (CWE-416 use-after-free) in the Windows Installer service. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N) confirms it requires local access and existing low-privileged authentication, with HIGH attack complexity - meaning exploitation depends on winning a race or satisfying specific timing/state conditions rather than a reliable single-shot trigger. The 7.0 base score is driven by total impact (C:H/I:H/A:H), and CISA's SSVC framework corroborates this with Technical Impact: total; however SSVC also reports Exploitation: none and Automatable: no, which strongly tempers urgency. No KEV listing and no POC are present in the input, and no EPSS score was provided, so there is no evidence of in-the-wild or imminent exploitation. Net assessment: a credible local privilege-escalation primitive worth patching in standard Microsoft Patch Tuesday cadence, but NOT an emergency - the HIGH complexity, local-only vector, authentication requirement, and 'Exploitation: none / Automatable: no' signals collectively indicate this is a high-severity-but-not-high-urgency issue rather than an actively dangerous one. One minor data note: the 'Denial Of Service' tag is somewhat inconsistent with the description, which characterizes the flaw as privilege elevation (the A:H impact is the only DoS-adjacent signal).

Exploit ScenarioDerived

A local attacker who already has a low-privileged foothold on a Windows host (e.g., a standard user account or a compromised low-integrity process) triggers a use-after-free condition in the Windows Installer service to corrupt memory and execute code in a higher-privilege (SYSTEM) context. Because the CVSS vector specifies HIGH attack complexity, success likely hinges on winning a race condition or achieving a precise memory state, so exploitation may require multiple attempts. No public exploit identified at time of analysis.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 14, 2026

Local privilege escalation in Microsoft Windows Installer (msiexec) lets an authenticated, low-privileged local user trigger a use-after-free and gain code execution at a higher integrity level, ultimately SYSTEM on affected Windows hosts. The vulnerability carries a CVSS 3.1 base score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning prior local access and a low-privileged foothold are required, and the high attack complexity implies the memory corruption depends on winning a timing or allocation race rather than succeeding reliably on a single attempt. Every currently supported Windows client and server edition is in scope, from Windows 10 1607/1809/21H2/22H2 through Windows 11 23H2/24H2/25H2/26H1/26H2 and Windows Server 2012 through Server 2025; vendor patches are available, CISA's SSVC assessment records exploitation as 'none' and the issue as not automatable, and no public exploit code has been identified at time of analysis.

RemediationAI

Vendor-released patch: apply the current Microsoft cumulative security update for each Windows branch, which brings affected systems to or above the fixed builds - 10.0.14393.9612 for the Server 2016/Windows 10 1607 line, 10.0.17763.9376 for Windows 10 1809 and Server 2019, 10.0.19044.7807 for Windows 10 21H2/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.26200.9711 for Windows 11 25H2, 10.0.28000.3231 for Windows 11 26H1, 10.0.26300.9711 for Windows 11 26H2, 10.0.20348.5761 for Windows Server 2022, and 6.2.9200.26434 / 6.3.9600.23470 for the legacy Windows Server 2012 and 2012 R2 lines; the authoritative guidance is at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85361. Because exploitation requires an already-authenticated local low-privileged session, the practical compensating controls are to remove or tightly scope local interactive logon and RDP rights for non-administrative users, avoiding shared low-privilege accounts on sensitive hosts; note the trade-off that this can disrupt legitimate multi-user workstation and help-desk workflows. Where the Installer is not business-critical, Windows Installer can be restricted via Group Policy (DisableMSI) or application allowlisting so that only administrators can initiate package install and repair operations, which removes the trigger surface for msiexec, but this will break user-driven software installation and some third-party updaters. Enhancing monitoring of msiexec.exe process creation and unexpected child processes, plus prompt rollback or rebuild of any host where a low-privileged user demonstrates unexpected elevated processes, provides a detection backstop; none of these controls substitute for patch deployment, and there is no evidence in the available data of active exploitation that would justify emergency isolation of unpatched hosts ahead of the normal update cycle.

Affected VersionsENISA

Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2012 fix: 6.2.9200.26434
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26434
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

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 flaw is a CWE-416 use-after-free, a memory-safety class in which an object is released back to the heap while a dangling reference to it remains and is later dereferenced, allowing an attacker to control the contents of the freed region and redirect execution or corrupt adjacent structures. The affected component is the Windows Installer service, the engine behind .msi and .msp package processing that runs with elevated (often SYSTEM) privileges; because the servicing and repair paths in msiexec handle transient heap objects and rollback state, the high attack complexity (AC:H) in the assessed vector is consistent with the corruption requiring a specific free/reallocate ordering or race window rather than a deterministic, single-shot trigger. The affected build thresholds supplied by EUVD span the full current Windows servicing tree - for example Windows 11 24H2 and Windows Server 2025 share the 10.0.26100 line (fixed at 10.0.26100.9711 and 10.0.26100.33650 respectively), Windows 11 25H2 sits on 10.0.26200 (<10.0.26200.9711), and the Windows Server 2012/2012 R2 legacy lines sit on 6.2.9200 and 6.3.9600 - confirming the vulnerable code is common to the Installer across all supported editions and that the attacker must already hold a local, low-privileged session (PR:L, UI:N) to reach it.

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

Vendor (microsoft) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local-only use-after-free (AV:L) requiring an existing low-privileged account (PR:L) and a race to trigger (AC:H), yielding full SYSTEM compromise (C/I/A:H).

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:20 cve.org
HIGH 7.0

DescriptionCVE.org

Use after free in Windows Installer allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A local privilege-escalation flaw in Microsoft Windows Installer (msiexec) affects every currently supported Windows client and server edition, from Windows 10 1607 through Windows 11 26H2 and Windows Server 2012 through Server 2025. An attacker who already holds a low-privileged account on a machine can elevate to SYSTEM, gaining full control of that host and a practical stepping stone for credential theft, lateral movement, and ransomware staging. Leadership should care because the affected footprint is effectively the entire Windows estate, and remediation requires coordinated, verifiable patching rather than any architectural change.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 85% exploitable
Prevalence
Ubiquitous
Windows Installer ships in every supported Windows client and server edition
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy