Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local foothold
-
DeliveryInvoke Windows Installer with crafted input
-
ExploitTrigger heap-based buffer overflow (CWE-122)
-
ExecutionCorrupt heap and hijack execution flow
-
ImpactElevate to SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK
1 technique across 1 tactic: Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the attacker to already possess authenticated local access to the target Windows host (PR:L) - this is a local privilege-escalation flaw (AV:L), not a remote one, so it cannot be reached across the network and is unsuitable for mass exploitation (SSVC Automatable=no). The attacker must be able to invoke the Windows Installer (msiexec/MSI service) and supply crafted input that overflows a heap buffer; no user interaction is needed (UI:N) and complexity is low (AC:L). The primary limiting factor is the required pre-existing foothold with some level of privilege, meaning this is realistically a second-stage escalation step rather than an initial-access vector. The affected component (Windows Installer) is present by default on all supported Windows client and server editions listed in the EUVD data, so no non-default configuration is required once local access is obtained. |
| Impact | This is a credible but not emergency-level priority. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 HIGH) describes a local privilege-escalation flaw requiring low-level authenticated access with no user interaction and low attack complexity, yielding total confidentiality, integrity, and availability impact on the local system. The CISA SSVC framework corroborates a measured risk posture: Exploitation=none (no observed or public exploitation), Automatable=no (cannot be mass-weaponized, consistent with a local-access precondition), but Technical Impact=total (full compromise of the affected component once exploited). There is no CISA KEV listing and no POC reported in the supplied data, so exploitation status is 'no public exploit identified at time of analysis.' No EPSS score was provided, so exploitation probability cannot be quantified from this input. The signals are internally consistent - a local-only EoP that is impactful but not remotely or automatically exploitable - so this is a real patch-management priority (classic second-stage escalation primitive) rather than an internet-facing fire drill. Note the one minor tension: the field states 'authorized attacker' while PR:L already encodes required privileges, confirming authentication is needed; this is not a contradiction but reinforces that an attacker must first gain a foothold. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged authenticated session on a Windows host (for example via phishing, stolen credentials, or an initial RCE) invokes the Windows Installer service with crafted input that triggers the heap-based buffer overflow, corrupting heap memory to hijack execution in a higher-privileged context and obtain SYSTEM-level control. No user interaction is required and attack complexity is low. No public proof-of-concept exploit was identified in the supplied data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in Microsoft Windows Installer (msiexec/msiserver) allows an authenticated attacker who already holds a low-privilege foothold on a Windows host to trigger a heap-based buffer overflow (CWE-122) and gain high-integrity/SYSTEM-level code execution with full confidentiality, integrity, and availability impact. The flaw affects essentially the entire supported Windows client and server estate documented by EUVD, from Windows 10 1607, Windows Server 2012 and 2012 R2 through Windows 11 26H2 and Windows Server 2025, and is exploitable with low attack complexity and no user interaction (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U, base 7.8). Because it is strictly local (AV:L) it cannot be reached across the network, and with CISA's SSVC recording Exploitation=none and Automatable=no, and no public exploit code identified at time of analysis, this is a credible second-stage escalation step for an attacker who has already landed on the box rather than a mass-exploitation or initial-access vector.
RemediationAI
Vendor-released patch: Microsoft has published fixes for this CVE, so the primary action is to apply the current cumulative Windows security update that brings each affected build to or above its fixed revision, per the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-85366 - namely Windows Server 2012 6.2.9200.26434, Server 2012 R2 6.3.9600.23470, Server 2016 and Windows 10 1607 10.0.14393.9612, Server 2019 and Windows 10 1809 10.0.17763.9376, Windows 10 21H2/22H2 10.0.19044.7807, Server 2022 10.0.20348.5761, Windows 11 23H2 10.0.22631.7652, Windows 11 24H2 and Server 2025 10.0.26100.9711 and 10.0.26100.33650 respectively, Windows 11 25H2 10.0.26200.9711, 26H2 10.0.26300.9711, and 26H1 10.0.28000.3231; prioritize servers and any host where non-administrative users are permitted interactive logons, since the flaw is a local escalation primitive that yields SYSTEM once an attacker has a foothold. Where immediate patching is not possible, compensating controls target the required invocation of the Installer rather than the bug itself: use AppLocker or WDAC to restrict execution of msiexec.exe so that only administrators can launch it and typical users cannot feed crafted packages into the service (trade-off: users lose the ability to self-install or repair MSI-packaged software, and installers invoked by software-deployment tooling must be explicitly allow-listed); optionally disable the Windows Installer (msiserver) service on hardened servers where no MSI-based installation, repair, or uninstall activity is expected (trade-off: MSI servicing is broken and the service is known to restart on demand, so this must be paired with a service-restart policy and change-controlled re-enablement to install patches); and, since exploitation requires an existing local low-privileged foothold, tighten who can log on interactively or via RDP to affected servers and monitor for unusual msiexec.exe child processes, unexpected MSI/MSI transform writes to user-writable paths, and privilege-boundary crossings from non-administrative accounts.
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
Windows Installer is the default MSI-based installation, servicing, and repair subsystem shipped with every supported Windows client and server edition; its core engine (msiexec.exe) runs under the msiserver service, and the service executes installation operations in a SYSTEM context. The vulnerability is a heap-based buffer overflow (CWE-122), meaning a length or size value used when allocating or copying into a heap allocation is not validated correctly, so an out-of-bounds write corrupts adjacent heap metadata and attacker-influenced objects. Reaching the bug requires an actor who can invoke the Windows Installer with crafted input (for example a malformed MSI package or transform supplied to an elevated install/repair path) while already having local low-privileged code execution on the host. The CVSS vector confirms the boundary being crossed is one of privilege, not of network reachability: PR:L and AV:L mean the attacker must already be running as an ordinary local user, while S:U with C:H/I:H/A:H reflects that a successful overflow yields code at the higher integrity level the Installer service operates at. The affected builds enumerated by EUVD (Windows 10 1607 through 22H2, Windows 11 23H2 through 26H2 and 26H1, and Server 2012 through Server 2025, including Server Core installations) all ship the vulnerable component by default, so no non-default configuration is a prerequisite once local access exists.
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:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Local-only privilege escalation requiring an existing low-privileged session (AV:L, PR:L), no user interaction, low complexity, yielding full local compromise (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Installer allows an authorized attacker to elevate privileges locally.
Executive ViewAI
CVE-2026-85366 is a high-severity local privilege escalation flaw in Microsoft Windows Installer affecting a broad range of supported Windows client and server versions, from Windows 10 1607 and Windows Server 2012/2012 R2 through Windows 11 26H2 and Windows Server 2025. An authenticated attacker who already has a low-privilege foothold on a host could escalate to SYSTEM-level control, enabling full compromise of that machine and potential lateral movement or data access. Because the vulnerable component is ubiquitous across the Windows estate, leadership should prioritize patching to reduce risk from insider threats or attackers who obtain initial access.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.
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-99490
GHSA-p2qg-7m57-397x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB