Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local session
-
DeliveryCraft object triggering SmartScreen type confusion
-
ExploitCorrupt memory via mismatched type
-
ExecutionExecute code in elevated context
-
ImpactEscalate to SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Type safety enforcement
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 | Requires an attacker to already have interactive, low-privileged local access and the ability to run code on the target Windows host - there is no remote or network vector (AV:L) and no path for an unauthenticated user (PR:L). Exploitation targets the Windows SmartScreen component, which is present by default, so no non-default feature toggle is implied by the description; however, the attacker must first establish a foothold and then successfully trigger and groom the type-confusion condition. Limiting factors per CISA SSVC: exploitation is not automatable and none has been observed, meaning realistic abuse is as a manual post-compromise escalation step rather than mass exploitation. The host must be running an affected build below the patched versions listed for each Windows release (e.g., Windows 11 24H2 below 10.0.26100.9711). |
| Impact | This is a moderate-priority, not top-tier, issue. The CVSS 3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects high technical impact but a constrained reach: exploitation is local (AV:L) and requires an attacker who is already authenticated with at least low privileges on the host (PR:L). It is an elevation-of-privilege flaw, so the value to an attacker is as a post-compromise escalation step, not an initial entry vector. The supporting signals downgrade urgency relative to the raw score: CISA SSVC lists Exploitation as 'none' and Automatable as 'no' (consistent with a local EoP that cannot be sprayed at scale), though Technical Impact is 'total'. There is no CISA KEV listing and no public proof-of-concept in the provided data, so exploitation status is 'no public exploit identified at time of analysis'. No EPSS score was provided, which is a gap - it would normally help rank this among the Patch Tuesday volume. Net: a genuine but non-emergency patch item best prioritized behind any remotely exploitable or actively-exploited bugs, while still deserving prompt remediation on multi-user or workstation hosts because the impact ceiling is full compromise of confidentiality, integrity, and availability. |
| Exploit ScenarioDerived | An attacker who has already gained low-privileged code execution on a Windows host (e.g., via phishing, a standard user account, or a prior foothold) invokes a crafted operation that triggers the type-confusion flaw in Windows SmartScreen, causing it to misinterpret a resource's type. By grooming the mismatched object, the attacker corrupts memory in a higher-privileged context and escalates to SYSTEM-level privileges. No public exploit code is identified at time of analysis, and the attack cannot be performed remotely or without an existing local session. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in Windows SmartScreen allows an attacker who already holds a low-privileged interactive session on a Windows host to corrupt memory through a type-confusion condition and elevate to a higher-integrity context, with full loss of confidentiality, integrity, and availability if successful. Exploitation is local only (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8): there is no remote or network vector, and the attacker must first establish code execution on the target before triggering the flaw. Microsoft has released fixes, and CISA's SSVC review rates exploitation as none observed and not automatable, so this is best treated as a manual post-compromise escalation step rather than a mass-exploitation threat; no public exploit code or KEV listing is associated with the CVE at time of analysis.
RemediationAI
Vendor-released patch: Microsoft has published fixed builds for every affected release - update Windows 10 1809/Server 2019 to 10.0.17763.9376 or later, Windows 10 21H2/22H2 to 10.0.19044.7807 or later, Windows Server 2022 to 10.0.20348.5761 or later, Windows 11 23H2 to 10.0.22631.7652 or later, Windows 11 24H2 to 10.0.26100.9711 or later, Windows 11 25H2 to 10.0.26200.9711 or later, Windows 11 26H2 to 10.0.26300.9711 or later, Windows 11 26H1 to 10.0.28000.3231 or later, and Windows Server 2025 (including Server Core) to 10.0.26100.33650 or later, applying the guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-70051. Prioritize this as a post-compromise-hardening update rather than an emergency-remotely-exploitable one, since the vector is local and non-automatable per SSVC; interim compensating controls include enforcing least privilege so that interactive users and service accounts cannot readily run arbitrary local code, enabling Exploit Protection mitigations such as Arbitrary Code Guard and Control Flow Guard for SmartScreen-related binaries where deployment tooling permits (with a possible performance and compatibility cost to legacy or unsigned applications), and tightening application allow-listing/AppLocker or WDAC policies to shrink the pool of binaries a low-privileged attacker can use to groom the type confusion. Disabling SmartScreen via policy is technically possible but is NOT recommended as a mitigation - it removes Mark-of-the-Web and reputation-based blocking for downloads and attachments, materially increasing phishing and malware risk while providing no confirmed protection against this specific bug.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 13 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 SmartScreen is the reputation and Mark-of-the-Web enforcement component built into the Windows Shell, Attachment Manager, and browser download flows; it inspects files and URLs before execution and is present by default across Windows client and server SKUs, which is why the vulnerable code path requires no special feature enablement. The root cause is CWE-843 (Access of Resource Using Incompatible Type, i.e. type confusion): the component processes a resource while treating it as a different type than it actually is, so subsequent field or vtable accesses land on attacker-influenced memory. In practice this class of bug in a privileged Windows component yields memory corruption that a local low-privileged process can groom into code execution in a higher-integrity context. Because the attack is delivered locally (AV:L) with low privileges required (PR:L) and no user interaction (UI:N), the realistic path is a compromised unprivileged process or user session pivoting to administrator/SYSTEM. Affected platforms span Windows 10 (1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), and Windows Server 2019, 2022, and 2025 including Server Core installations, all below their respective patched build numbers.
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 EoP requiring an existing low-privileged session (AV:L, PR:L); no user interaction and a reliable type-confusion trigger (UI:N, AC:L) yielding full SYSTEM compromise (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Access of resource using incompatible type ('type confusion') in Windows SmartScreen allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A high-severity flaw in Microsoft Windows SmartScreen lets someone who already has a limited, low-privilege session on a Windows machine escalate to a higher-integrity level, gaining full control over that device's data, its integrity, and its availability. Because the attacker must already be running code on the host, this does not open a new way into the environment; instead it magnifies the damage of any endpoint already compromised, turning a minor foothold into complete control of the machine and a likely stepping stone for lateral movement. Leadership should treat this as a routine patch-priority item rather than an emergency: Microsoft has shipped fixes, CISA has observed no exploitation and rates the flaw as not automatable, and no public exploit code was identified at the time of analysis.
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
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.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-99859
GHSA-77rw-v2rq-w874
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB