EUVD-2026-99749
GHSA-vfr4-7w83-492c
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privileged local access
-
DeliveryInteract with Assigned Access component
-
ExploitInject malicious code (CWE-94)
-
ExecutionEscape kiosk/user context
-
ImpactExecute as higher privilege
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Code injection prevention, sandbox exec
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Initial Access The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires that the target Windows host has the Assigned Access (kiosk mode) feature configured, and that the attacker already possesses low-privileged authorized local access (PR:L) to the system - this is not a default-enabled attack surface, since Assigned Access must be explicitly set up by an administrator. Limiting factors: the attacker must be local (AV:L, no network path), must already be authenticated/authorized, and the vulnerable kiosk configuration must be in use; no user interaction by a victim is required (UI:N). Affected builds span Windows 10 (21H2/22H2, 1809), Windows 11 (23H2/24H2/25H2/26H1/26H2), and Windows Server 2019, each fixed in the vendor-specified build thresholds. |
| 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, 7.8 HIGH) describes a local privilege-escalation flaw requiring the attacker to already have low-privileged authenticated access to the host - it is NOT remotely exploitable despite the 'RCE' tag in the input, which appears mislabeled. CISA's SSVC decision framework reinforces lower urgency: Exploitation=none (no observed or public exploitation), Automatable=no (cannot be mass-scripted at scale, consistent with a local EoP that needs an existing foothold), yet Technical Impact=total (full compromise of the vulnerable component, matching C:H/I:H/A:H). No EPSS score, KEV listing, or POC was provided in the input. The signals are internally consistent - a high-impact-but-locally-constrained bug - rather than conflicting. The practical priority is driven by the fact that a patch exists and total compromise is possible, but mitigated by the local-access requirement and the absence of any exploitation evidence, so this belongs in a standard Patch-Tuesday remediation cycle rather than an out-of-band emergency response. |
| Exploit ScenarioDerived | An attacker who already has a low-privileged interactive or authenticated session on a Windows machine configured with Assigned Access (kiosk mode) injects crafted code through the Assigned Access component to break out of the restricted context and execute code at a higher privilege level. No public exploit code was identified in the provided data, and the attack cannot be performed remotely or without an existing local foothold. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Local privilege escalation in Windows Assigned Access (kiosk mode) allows an authenticated, low-privileged local user to inject and execute code in a higher-integrity context, yielding full loss of confidentiality, integrity, and availability on the affected host (CVSS 3.1 base 7.8). Exploitation is constrained: the attacker must already hold authorized local logon (PR:L), the host must be one where an administrator has explicitly configured Assigned Access, and there is no network vector and no victim interaction (AV:L/UI:N). No public exploit code has been identified at time of analysis, no active exploitation is confirmed, and Microsoft has shipped fixed builds, so this is a credible but not emergency-level priority.
RemediationAI
Vendor-released patch: install the Microsoft cumulative update referenced by the MSRC advisory for CVE-2026-96220, which moves affected systems to the fixed builds 10.0.17763.9376 (Windows 10 1809 / Server 2019 and Server Core), 10.0.19044.7807 and 10.0.19045.7807 (Windows 10 21H2/22H2), 10.0.22631.7652 (Windows 11 23H2), 10.0.26100.9711 (24H2), 10.0.26200.9711 (25H2), 10.0.28000.3231 (26H1), and 10.0.26300.9711 (26H2), using the guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96220. If patching cannot be done immediately, note that exploitation requires a locally configured Assigned Access deployment, so the most effective compensating control is to remove or disable kiosk-mode/Assigned Access configuration on hosts that do not require it, at the cost of losing the kiosk lockdown for any legitimate shared-workstation use case. Where kiosk mode must remain, restrict interactive and secondary logon rights so that only tightly managed dedicated accounts can sign in to those machines, and audit kiosk configuration changes and unexpected child-process creation by kiosk accounts; these controls reduce but do not eliminate the attack surface, since the flaw is exercised in the local privilege boundary the feature is supposed to enforce. Because exploitation is local only and no public exploit code or active exploitation has been identified, web-facing or perimeter mitigations are not applicable here.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 10 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 CWE-94 improper control of code generation (code injection) flaw in the Windows Assigned Access feature, the kiosk-mode subsystem that pins a local account to a single approved application or restricted shell. Because Assigned Access relies on administrator-supplied configuration describing which processes to launch and how to constrain them, a code-generation or input-handling gap in that path lets a user who can already run code as a low-privileged kiosk account induce the feature to build or launch code outside the intended restricted context. The result is local elevation of privilege to a higher-integrity token, consistent with the assessed vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H - low attack complexity and no required user interaction, but strictly local access and low prior privileges, with impact confined to the host (Scope:U). Affected builds span Windows 10 (1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), and Windows Server 2019 including Server Core installations, each remediated by a build threshold supplied through Microsoft's update guide.
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 by an already-authorized low-privileged user (AV:L, PR:L), reliably triggerable (AC:L) with no victim interaction, yielding full compromise (C/I/A:H).
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Improper control of generation of code ('code injection') in Windows Assigned Access allows an authorized attacker to elevate privileges locally.
Executive ViewAI
A privilege-escalation flaw in Microsoft Windows Assigned Access, the kiosk-mode feature used to lock shared and public-facing devices to a restricted experience, allows a user who already holds a valid local logon on such a device to elevate to a higher-integrity context and take full control of that machine. Only Windows hosts where an administrator has deliberately configured Assigned Access are in scope, the attack is unauthenticated from a network standpoint but requires local logon, and no public exploit identified at time of analysis means this is a patch-driven hygiene issue rather than an emergency. Leadership should care because kiosk devices typically sit in lobbies, retail floors, clinics, and factory stations where full host compromise can expose any data or credential reachable from that endpoint and can serve as a staging point for lateral movement.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
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
Code injection occurs when an application accepts user input and passes it directly into a language interpreter or evaluator without proper sanitization.
Remote Code Execution represents the critical moment when an attacker successfully runs arbitrary code on a target system without physical access.
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
Exploit-DB