Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege local access
-
DeliveryInvoke Smart Card operation to free object
-
ExploitWin race to reclaim freed memory
-
ExecutionExecute controlled code via dangling pointer
-
ImpactElevate to SYSTEM privileges
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation 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 low-privilege local access to the target Windows system (PR:L, AV:L) - this is a post-compromise privilege-escalation primitive, not a remote entry point. The attacker must interact with the Windows Smart Card subsystem to trigger the use-after-free condition. Key limiting factors: the attack is local-only (no network reach), requires valid credentials or existing code execution, and carries high attack complexity (AC:H), meaning a race or specific timing/memory-state window must be won for reliable exploitation; no user interaction is needed (UI:N). The Smart Card component is present by default on all supported Windows versions, so no special non-default configuration is required to reach the vulnerable code. |
| Impact | This is a genuine but not top-tier priority. The CVSS 3.1 base score of 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) reflects full confidentiality, integrity, and availability impact once exploited, but the vector itself tempers real-world risk: exploitation is local (AV:L), requires an already-authenticated low-privilege user (PR:L), and is high-complexity (AC:H), which typically implies a race condition or timing window inherent to use-after-free flaws. These mitigating factors are corroborated by CISA's SSVC assessment: Exploitation=none (no observed exploitation), Automatable=no (cannot be reliably mass-exploited), and Technical Impact=total (consistent with the full-impact CVSS). There is no CISA KEV listing and no public proof-of-concept, so this is no public exploit identified at time of analysis. No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be factored in - this is a data gap, not a low score. In sum, the signals are internally consistent: a high-impact local privilege-escalation bug that is hard to exploit and not currently weaponized, making it a standard patch-cycle item rather than an emergency, though it is valuable to attackers as a post-compromise escalation primitive once initial access is achieved. |
| Exploit ScenarioDerived | An attacker who has already gained low-privileged code execution on a Windows host (e.g., via phishing or a compromised standard user account) runs a crafted program that abuses the Smart Card subsystem to trigger a use-after-free, winning a timing race to reclaim the freed memory. Successful exploitation elevates the attacker to higher (likely SYSTEM) privileges locally. No public exploit code is known, and the high attack complexity (AC:H) makes reliable exploitation non-trivial. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Local privilege escalation in the Windows Smart Card subsystem allows an attacker who already holds authenticated low-privilege access on a target host to corrupt memory through a use-after-free (CWE-416) and elevate to a higher-integrity context, including SYSTEM, with high impact to confidentiality, integrity, and availability (CVSS 3.1 base 7.0, vector AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). The attack is local-only and requires a race or specific timing/memory-state window to be won (AC:H), so it is a post-compromise escalation primitive rather than a remote entry point; no user interaction is required and the Smart Card component ships enabled by default on all supported Windows releases, so no special configuration is needed to reach the flawed code. Microsoft has released vendor fixes, and no public exploit code or confirmed active exploitation has been identified at time of analysis (CISA SSVC exploitation: none).
RemediationAI
Vendor-released patch: Microsoft fixed this issue in the monthly Windows cumulative updates tracked under MSRC advisory CVE-2026-83584 (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83584); apply the update that brings each affected install to or above its fixed build - 10.0.14393.9612 (Windows 10 1607 / Server 2016), 10.0.17763.9376 (Windows 10 1809 / Server 2019), 10.0.19044.7807 (Windows 10 21H2), 10.0.19045.7807 (Windows 10 22H2), 10.0.22631.7652 (Windows 11 23H2), 10.0.26100.9711 (Windows 11 24H2), 10.0.26200.9711 (Windows 11 25H2), 10.0.28000.3231 (Windows 11 26H1), 10.0.26300.9711 (Windows 11 26H2), 10.0.20348.5761 (Server 2022), 10.0.26100.33650 (Server 2025), 6.2.9200.26434 (Server 2012) and 6.3.9600.23470 (Server 2012 R2). The Smart Card service is loaded by default and is not directly exposed to the network, so the practical mitigation is patch velocity rather than attack-surface reduction; where patching must be deferred, the primary compensating control is to stop and disable the Smart Card service (SCardSvr) and the Smart Card Device Enumeration Service on hosts that do not use smart cards for logon or certificate operations, accepting that this breaks PIV/CAC logon, virtual smart cards, Windows Hello for Business certificate trust, and some VPN/RDP smart-card authentication flows. Secondary controls follow from the required PR:L precondition: restrict and monitor interactive and RDP local logon so that unprivileged or untrusted accounts cannot establish a foothold from which to run the privilege-escalation primitive, apply least privilege and remove local admin rights from standard users, and enable exploit-protection features such as Arbitrary Code Guard/CFG and Windows Defender ASR rules - noting these reduce but do not eliminate exploitability given that only patch-level remediation removes the use-after-free. No public exploit code is known, so emergency out-of-band action is not indicated, but the update should be scheduled within normal Patch Tuesday cycles.
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 flaw is a use-after-free (CWE-416) in the Windows Smart Card stack - the component exposed through winscard.dll and the Smart Card service (SCardSvr) that brokers communication between applications and smart card readers, cryptographic service providers, and the base CSP/KSP for certificate-backed logon. A use-after-free means the vulnerable code retains and later dereferences a pointer to a heap object (likely a context, card handle, or I/O buffer structure) after it has been freed, allowing the attacker to influence or reclaim that memory and redirect execution toward a privileged context. The provided tags (Use After Free, Memory Corruption, Denial Of Service) and the CVSS impact triad (C:H/I:H/A:H) indicate the primitive can be pushed beyond a crash into full integrity compromise. Because the CVSS vector is AV:L/AC:H/PR:L/UI:N, exploitation presumes an attacker who is already running code or holding credentials on the box and can repeatedly drive Smart Card API operations to win the memory-reuse window; AC:H reflects that the heap grooming and timing are non-trivial, while the default-on nature of the Smart Card subsystem across Windows 10, Windows 11, and Windows Server 2012 through 2025 means the vulnerable surface is universally reachable on affected builds.
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:H/PR:L/UI:N/S:U/C:H/I:H/A:H
Local post-authentication use-after-free (AV:L, PR:L) with a race-condition timing window (AC:H) yielding full SYSTEM compromise, hence C:H/I:H/A:H and scope unchanged.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Use after free in Windows Smart Card allows an authorized attacker to elevate privileges locally.
Executive ViewAI
The Windows Smart Card subsystem contains a high-severity local privilege escalation vulnerability (CVE-2026-83584) that could allow an attacker with authenticated low-privilege access to gain SYSTEM-level control, compromising confidentiality, integrity, and availability of affected hosts. Although no public exploit identified at time of analysis, the flaw affects default Windows installations and requires no special configuration, making it a valuable post-compromise escalation primitive. Leadership should prioritize patching to prevent attackers from escalating privileges and moving laterally within the environment.
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
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
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.
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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-99306
GHSA-873j-3gx2-3f89
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB