Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local foothold
-
DeliveryInvoke vulnerable Windows Installer path
-
ExploitOverflow stack buffer with crafted input
-
ExecutionOverwrite return address/control data
-
PersistExecute code as SYSTEM
-
ImpactFull host compromise
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack 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 an authenticated low-privileged local session on the target Windows system (CVSS PR:L, AV:L) - there is no remote or network-triggerable path and no user interaction by a victim is involved (UI:N). The vulnerable component is Windows Installer (msiexec/MSI processing), present by default in all supported Windows editions, so no non-default configuration is needed to reach the code. The principal limiting factor is the local-access prerequisite: an attacker without an existing foothold cannot reach this vulnerability, which is why SSVC rates it Automatable:no. It is realistically used as a privilege-escalation link in a larger intrusion chain rather than as an initial-access vector. |
| Impact | This is a credible but not emergency-priority local privilege-escalation flaw. 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) is internally consistent: it requires local access and some existing privileges (PR:L) but no user interaction, and yields total confidentiality, integrity, and availability impact - matching the SSVC 'Technical Impact: total' rating. However, the exploitation signals argue against treating this as a top-of-queue item: it is NOT in CISA KEV, SSVC reports 'Exploitation: none' (no observed or public exploitation), 'Automatable: no' (cannot be reliably weaponized at scale because an attacker must already have a local foothold), and no POC or EPSS score was provided in the input. These signals are consistent with each other - all pointing to low current real-world exploitation despite the high technical impact. The practical risk is therefore moderate: dangerous as a post-compromise escalation primitive (e.g., chained after phishing or an initial RCE) but not a mass-exploitable remote threat. EPSS data was not supplied, so probabilistic exploitation likelihood could not be weighed; this is a gap rather than a conflict. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged local account on a Windows host (for example after phishing, malware drop, or a prior foothold) invokes the vulnerable Windows Installer (msiexec) code path with crafted input that overflows a stack buffer, overwriting control data to execute code in the context of the SYSTEM-level installer service. This converts limited user access into full SYSTEM control. No public exploit code was identified at time of analysis, and CVSS AC:L indicates the overflow is reliably triggerable once local access is obtained. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
A stack-based buffer overflow (CWE-121) in the Windows Installer component (msiexec/MSI package processing) allows an authenticated local attacker holding a low-privileged session to elevate to higher privileges, including SYSTEM, with high confidentiality, integrity, and availability impact (CVSS:3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is reachable in the default configuration of all supported Windows client and server editions, but exploitation requires an existing local foothold and no victim interaction, so it is best characterized as a privilege-escalation link in a broader intrusion chain rather than an initial-access vector. No public exploit code has been identified at time of analysis and the flaw is not listed as confirmed actively exploited (CISA KEV); CISA's SSVC assessment rates exploitation as none, automatable as no, and technical impact as total. A vendor patch is available per Microsoft's MSRC update guide.
RemediationAI
Apply the vendor patch: Microsoft has released fixes for this issue per its MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83767), distributed through the normal Windows cumulative update channels. The advisory-listed patched build levels that resolve the vulnerability are 10.0.14393.9612 for Windows 10 1607 and Server 2016, 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.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 Server 2022, 10.0.26100.33650 for Server 2025 (including Server Core), 6.2.9200.26434 for Server 2012, and 6.3.9600.23470 for Server 2012 R2; systems on out-of-support builds should be upgraded to a supported release, since no patch will be issued for them. Because the attacker must already hold a local low-privileged session, the highest-value compensating control is reducing that foothold: enforce least privilege so users do not run as administrators, restrict interactive logon and RDP access to trusted accounts, and block untrusted users from local sign-on, accepting the operational cost that this limits legitimate workstation sharing and remote administration. Where MSI-based software deployment is not required on a given host, disabling the Windows Installer service (via the service control manager or the DisableMSI policy, which can be set to hide or restrict installer usage for non-administrators) removes the attack surface, with the trade-off that application installs, repairs, and some updaters will fail until it is re-enabled; note that DisableMSI does not fully prevent administrators from invoking msiexec. Application control (WDAC/AppLocker) and restricting who may author or provide MSI packages to a machine further reduce the ability to deliver crafted installer input. Monitor for abnormal msiexec.exe child processes or unexpected privilege transitions originating from standard user sessions, since discovery and lateral movement in an intrusion chain typically precede this type of local escalation. No public exploit code has been identified at time of analysis, but that does not reduce the importance of prompt patching.
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 classic stack-based buffer overflow (CWE-121) in Windows Installer, the service and API set (msiexec.exe, msi.dll) that parses and executes MSI installation packages and patches. The root-cause class means a length or size assumption is violated when copying data into a fixed-size stack buffer, allowing adjacent stack memory - including saved return addresses or function pointers - to be overwritten and execution redirected under the caller's security context. Because Windows Installer runs with elevated privileges when servicing machine-wide installations, a low-privileged local user who can supply or trigger crafted MSI input can convert that overflow into privilege escalation up to SYSTEM. The component ships enabled by default across all affected editions (Windows 10, Windows 11, and Windows Server 2012 through 2025), so no non-default configuration is required to reach the vulnerable code path. The CVSS vector AV:L/PR:L with UI:N confirms the access prerequisite is a local, already-authenticated low-privileged session, with no network vector and no victim interaction; per the independent assessment, exploitation can only be reached from an existing foothold, which is consistent with SSVC marking the issue non-automatable.
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 privilege escalation requiring an existing low-priv account (AV:L, PR:L), reliably triggerable (AC:L), no victim interaction (UI:N), yielding SYSTEM-level total impact (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Stack-based buffer overflow in Windows Installer allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A high-severity memory corruption flaw in the Windows Installer component (msiexec/MSI package processing) affects all supported Windows client and server editions in their default configuration, allowing an attacker who already holds a low-privileged local session to escalate to SYSTEM-level privileges. The practical consequence for the organization is that any single compromised workstation or server account - including service accounts and standard user desktops - can be converted into full administrative control of that host across confidentiality, integrity, and availability. Leadership should treat this as an escalation enabler inside a broader intrusion chain rather than an external entry point: it does not grant initial access, but it materially raises the value of even a minor local foothold and therefore the speed at which an incident can spread.
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 stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.
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-99988
GHSA-v5ch-2mr4-rg29
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB