Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local account
-
DeliveryInvoke Windows Installer with crafted malformed input
-
ExploitTrigger stack buffer overflow in Installer component
-
ExecutionOverwrite saved return address on stack
-
PersistRedirect execution to attacker-controlled code
-
ImpactExecute arbitrary commands at SYSTEM privilege
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 an authenticated local session on the target host; the CVSS PR:L metric confirms that a standard low-privileged account - not an administrator - is sufficient to trigger the vulnerable Windows Installer code path. The attack vector is strictly local (AV:L), meaning remote unauthenticated exploitation is not possible without a prior initial access step such as credential theft, phishing, or a separate remote vulnerability. No user interaction beyond the attacker invoking the installer subsystem is required (UI:N). Windows Installer is enabled and active by default on all affected Windows editions, so no non-default configuration is required to reach the vulnerable code. Exploitation is limited by the requirement for any local account access; systems where only highly trusted accounts can log on locally present a reduced effective attack surface. |
| Impact | The CVSS 3.1 score of 7.8 with vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H accurately captures the threat profile: once an attacker holds any low-privileged local account, exploitation is straightforward with no user interaction required. The lack of a CISA KEV entry and the absence of reported public POC code suggest this has not yet seen widespread in-the-wild abuse, which partially tempers immediate urgency compared to actively exploited LPE chains. EPSS data was not supplied, so probabilistic exploitation likelihood cannot be quantified from this dataset alone; risk prioritization should instead weight the extremely broad affected surface - spanning desktop Windows 10 and 11 across multiple feature releases, plus every major Server edition from 2012 to 2025 - meaning even a mid-sized municipal IT team in olsztyn should treat this as urgent given the sheer volume of endpoints requiring patching. The AC:L rating is the most concerning signal: unlike AC:H flaws that require race conditions or specific timing, this overflow is reliably triggerable, making it a prime candidate for inclusion in post-exploitation toolkits once public research matures. |
| Exploit ScenarioDerived | An attacker who has obtained a standard low-privileged local or domain user account on a target Windows host crafts a malformed MSI package or invokes Windows Installer APIs with input designed to overflow the stack buffer in the vulnerable component. The overflow corrupts the saved return address on the stack, redirecting execution to attacker-controlled code or a ROP gadget chain that executes at SYSTEM privilege. No public POC has been identified at time of analysis, but the AC:L CVSS rating indicates the overflow condition is reliably reproducible without complex preconditions such as race conditions or heap spray. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Aug 11, 2026
Stack-based buffer overflow in Windows Installer enables local privilege escalation across a wide range of Microsoft Windows desktop and server editions. An authenticated low-privileged local user can exploit the flaw (CWE-121) to achieve SYSTEM-level code execution, with full confidentiality, integrity, and availability impact on the compromised host. No public exploit code or CISA KEV listing has been identified at time of analysis; however, the low attack complexity and broad affected surface spanning Windows 10 through Windows 11 and Windows Server 2012 through 2025 make this a high-priority patching target.
RemediationAI
Apply the Microsoft security update for CVE-2026-62768, delivered via Windows Update, WSUS, or the Microsoft Update Catalog. The fixed builds per product line are: Windows 10 1607 and Server 2016 require build 10.0.14393.9418 or later; Windows 10 1809 and Server 2019 require 10.0.17763.9115 or later; Windows 10 21H2 requires 10.0.19044.7663 or later; Windows 10 22H2 requires 10.0.19045.7663 or later; Windows Server 2022 requires 10.0.20348.5499 or later; Windows 11 23H2 requires 10.0.22631.7517 or later; Windows 11 24H2 requires 10.0.26100.9168 or later while Server 2025 requires 10.0.26100.33296 or later; Windows 11 25H2 requires 10.0.26200.9168 or later; Windows 11 26H1 requires 10.0.28000.2704 or later; Windows Server 2012 requires 6.2.9200.26279 or later; and Windows Server 2012 R2 requires 6.3.9600.23337 or later. Consult the full advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-62768. Where patching cannot be applied immediately, restrict the set of accounts with interactive local logon rights using Group Policy (Deny log on locally), and enforce application control policies (AppLocker or WDAC) to prevent execution of unsigned or untrusted MSI packages - note these controls reduce exposure but do not eliminate risk for accounts legitimately permitted to run installers.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 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 (msiexec.exe and associated msi.dll subsystem) is the native Windows package management engine present by default on all supported Windows editions; it runs with elevated SYSTEM privileges during install, repair, and removal operations. CWE-121 (Stack-Based Buffer Overflow) describes a condition where a fixed-size stack buffer is written beyond its allocated bounds, corrupting adjacent stack data - including saved return addresses or frame pointers - that can be redirected to attacker-controlled code. Because the Windows Installer service operates at elevated privilege, a standard user who can invoke the vulnerable code path gains an immediate escalation path to SYSTEM. The CVSS vector AV:L/AC:L/PR:L confirms the flaw is in the local execution path, requires only a standard user account (PR:L), and presents no special complexity barriers (AC:L). Affected CPE data spans Windows build families from 6.2.x (Server 2012) through 10.0.28000.x (Windows 11 26H1), indicating the vulnerable code has been present in the Installer component across more than a decade of Windows releases.
Know when Windows 10 1607 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 attack path with low-privilege account sufficient; full CIA impact from SYSTEM-level execution; no scope change as impact remains within the target OS security boundary.
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
Windows Installer contains a stack-based buffer overflow affecting Windows 10, Windows 11, and Server editions 2012-2025, enabling local privilege escalation to SYSTEM-level access. Authenticated low-privileged users can exploit this flaw to gain complete control over affected systems, compromising confidentiality, integrity, and availability across potentially thousands of enterprise endpoints.
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.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-56657
GHSA-rq77-ppj7-934x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB