Windows 11 26h1
Monthly
Remote code execution is possible in the Microsoft PostScript Printer Driver, where a heap-based buffer overflow (CWE-122) lets an unauthenticated attacker who can deliver crafted PostScript print data over the network corrupt heap memory and execute arbitrary code in the context of the Windows Print Spooler. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication and no user interaction are required; every supported Windows client and server release from Windows Server 2012 through Windows 11 26H2 and Windows Server 2025 is affected unless it has been updated to the fixed build listed by Microsoft. Vendor patches are available, and no public exploit code or active exploitation has been identified at time of analysis - SSVC records exploitation as 'none' - so the practical exposure is driven by whether the print/spooler service is reachable from untrusted networks.
Local privilege escalation in the Windows Win32 kernel subsystem allows an authenticated attacker running as a low-privileged user to abuse a use-after-free condition in a kernel object and elevate to full system privileges, with high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Only specific Windows 11 builds (23H2, 24H2, 25H2, 26H1, 26H2) and Windows Server 2025 (including Server Core) below Microsoft's fixed builds are affected; exploitation is not remote, requires no user interaction, and hinges on winning a timing-dependent race window, which lowers exploit reliability. No public exploit identified at time of analysis, CISA's SSVC assessment records exploitation as 'none' and automatable as 'no', and Microsoft has shipped a vendor patch, so fully updated hosts are not exploitable - the overall priority is moderate rather than emergency.
A heap-based buffer overflow in the Windows Network File System (NFS) Server role lets an attacker who already holds local, low-privileged authenticated access on a Windows host execute code in a higher-privileged context, with high impact to confidentiality, integrity, and availability (CVSS 3.1 base 7.8, AV:L/PR:L/UI:N). Exploitation is constrained by prerequisites: the optional NFS Server / Services for NFS feature must actually be installed and enabled - it is absent from default Windows installations - and the attacker must already be on the box with valid low-privilege credentials; no user interaction is required. Vendor-released patches exist for all listed Windows client and server builds, no public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV), so this is a moderate-to-serious patching priority rather than a top-tier emergency. Defenders should note the scoring discrepancy flagged in the independent assessment: NFS is a network-facing service, yet Microsoft scored the vector as LOCAL - confirm via the MSRC advisory whether any network-adjacent trigger path exists beyond the local vector.
Local privilege escalation in the Windows Update Service allows an authenticated, low-privileged user on Windows 11 (23H2, 24H2, 25H2, 26H1 and 26H2) or Windows Server 2025 to run code as SYSTEM by placing a malicious module in a directory the service searches ahead of the trusted location (CWE-426 untrusted search path, CVSS 7.8, vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not remote: an attacker must already hold a local authenticated account with write access to a directory in the service's search order, and CISA's SSVC assessment records exploitation as none, automatable as no and technical impact as total, making this a manual post-compromise escalation rather than a self-propagating or wormable issue. No public exploit code was identified at time of analysis, and Microsoft has published fixing updates through its MSRC Update Guide.
Local privilege escalation in the Windows Audio Service lets an attacker who already holds low-privilege code execution on a Windows host trigger a use-after-free (CWE-416) and elevate to a more privileged context. The flaw is rated CVSS 7.0 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H): it is not remotely reachable, requires an existing foothold and local code execution, and the high attack complexity reflects a race/timing window that must be won, making exploitation non-deterministic. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records exploitation as none and non-automatable, and the issue does not appear in CISA KEV; completely patched builds are available from Microsoft.
Local privilege escalation in the Windows Update Service lets an authenticated attacker with low-level local access (CVSS PR:L/AV:L) corrupt heap memory to gain SYSTEM-level code execution on unpatched Windows client and server builds. The flaw is a heap-based buffer overflow (CWE-122) that requires no user interaction and no special configuration, since the Windows Update Service is enabled by default; exploitation cannot be automated or performed remotely, and no public exploit code or active exploitation has been identified at time of analysis.
Local privilege escalation in Microsoft Windows OLE allows an attacker who already holds low-privileged authenticated access on a host to drive a heap-based buffer overflow by inducing the vulnerable component to process a crafted OLE object, resulting in code execution at a higher integrity level with complete loss of confidentiality, integrity, and availability (CVSS 7.8, CWE-122). The issue spans a wide set of unpatched Windows client and server builds, including Windows 10 21H2/22H2, Windows 11 23H2 through 26H2, and Windows Server 2012, 2012 R2, 2016, 2019, 2022, and 2025; vendor fixes are available and no public exploit code was identified at time of analysis. Because the attack is local (AV:L), requires existing credentials (PR:L), needs no victim interaction (UI:N), and is classified as non-automatable with exploitation 'none' under CISA's SSVC framework, it is a second-tier, post-compromise escalation primitive rather than a remote or wormable threat.
Local privilege escalation in the Microsoft Windows Search component lets an authenticated attacker with a low-privileged local account corrupt memory and potentially execute code at a higher integrity level. The flaw is a use-after-free (CWE-416) rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation is local, requires prior authentication, needs no user interaction, and carries high attack complexity because the attacker must reliably reclaim a freed object. Microsoft has released vendor patches; no public exploit code has been identified, and CISA's SSVC assessment records exploitation as none with the issue not automatable (technical impact: total).
Local privilege escalation in the Windows Event Tracing (ETW) subsystem allows an attacker who already holds low-privileged code execution on a host to raise their privileges, with high confidentiality, integrity and availability impact (CVSS 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). The root cause is a use-after-free (CWE-416) that is only reachable locally and additionally requires winning a timing race, so reliable exploitation is non-trivial; no public exploit identified at time of analysis and the flaw is not listed in CISA KEV, with CISA SSVC scoring exploitation as 'none' and automatable as 'no'. Microsoft has released a vendor patch, and risk is concentrated on multi-user, terminal/RDP, or shared systems where untrusted low-privilege accounts can run code - a moderate, not emergency, priority.
Network denial of service in Windows SMB Server allows unauthenticated remote attackers to make the service allocate resources without throttling, exhausting memory or handles until SMB-dependent services and, potentially, the host become unresponsive. Tracked as CWE-770 and scored 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), it affects Windows 10 (1607 through 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1/26H2) and Windows Server 2012 through Server 2025, with impact confined to availability - there is no disclosure or code-execution path. No public exploit has been identified at time of analysis, CISA's SSVC assessment records exploitation as 'none' (automatable: yes, technical impact: partial), and vendor-released patches are available through the Microsoft update guide referenced by the advisory.
Local privilege escalation in the Windows Portable Device File System Driver lets an authenticated, low-privileged attacker who already has code execution on a Windows host trigger a heap-based buffer overflow (CWE-122) and elevate to SYSTEM. The flaw spans an unusually wide set of builds - Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2), and Windows Server 2012 through 2025, including Server Core installations - and carries a vendor CVSS of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Microsoft has released fixes, CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', and no public exploit code has been identified at time of analysis; the operative constraint is the required local foothold, which makes this a second-stage escalation primitive rather than an entry point.
Heap-based buffer overflow in Microsoft Windows Media Foundation allows a local attacker to elevate privileges on affected Windows hosts by supplying a crafted media file that the logged-in user opens, previews, or otherwise has parsed by the platform's media pipeline. Successful exploitation is assessed at CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-122), yielding high confidentiality, integrity, and availability impact; because the vector is local with a user-interaction prerequisite, the attacker must first land the file on the target and induce the user to process it, which makes this a credible but interaction-gated escalation path rather than a network-facing exploit. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV); a vendor patch is available, and fully updated builds (those at or above the version thresholds enumerated in the EUVD affected-version data) are not affected. Despite being an LPE rather than an RCE, the no-privilege prerequisite, low complexity, and full three-property impact keep this a legitimate prioritization candidate in environments where media files are routinely handled.
Memory-safety failure in the Windows Bluetooth Port Driver lets a device within Bluetooth radio range trigger out-of-bounds memory access that can escalate to code execution on unpatched Windows 10, Windows 11, and Windows Server hosts with an active Bluetooth radio. Exploitation requires proximity (adjacent network), the victim's Bluetooth to be enabled and in use, some form of user interaction such as accepting or initiating a Bluetooth connection, and high attack complexity reflecting preconditions outside the attacker's control; authentication is not required (CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H). Microsoft has shipped fixes, no public exploit code has been identified at time of analysis, CISA's SSVC assessment records exploitation as "none" with the attack assessed as non-automatable, and hosts with Bluetooth disabled are not exposed - making this a moderate rather than top-tier priority despite the 7.1 score and the CVSS "total" technical impact rating on affected devices.
Local privilege escalation in the Microsoft Graphics Component affects multiple Windows client and server builds, allowing a local, authenticated attacker with low privileges (CVSS AV:L/PR:L) to exploit a numeric truncation error and gain High confidentiality, integrity, and availability impact after corrupting heap memory. The vulnerability has a CVSS 3.1 base score of 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), requires no user interaction, and is not a remote entry point; no public exploit was identified at time of analysis, and no EPSS score was provided. A vendor patch is available per Microsoft, so affected organizations should prioritize update deployment on all listed Windows versions and Server Core installations.
Local privilege escalation in the Windows Kernel allows an authenticated low-privilege attacker with existing code execution on a target host to trigger a heap-based buffer overflow and elevate privileges in kernel mode. Affected default installations include Windows 10, Windows 11 21H2 through 26H1, and Windows Server 2019/2022/2025 builds below the vendor-patched build levels. No public exploit identified at time of analysis and CISA SSVC reports no exploitation; a vendor patch is available.
Local privilege escalation in the Windows Audio Service (audiosrv) affects Windows 11 versions 24H2, 25H2, 26H1 and 26H2 as well as Windows Server 2025 (including Server Core), allowing an attacker who already holds a low-privileged foothold on the host to execute code in a more privileged context. Exploitation requires an authenticated local attacker with the ability to interact with the audio service (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), and the high attack complexity indicates the use-after-free hinges on a race or specific heap/object state that is difficult to trigger reliably; the service runs by default, so every affected build is exposed once a foothold exists. There is no public exploit identified at time of analysis, CISA SSVC records exploitation as none and the issue is not automatable, so this is a genuine but moderate-priority local privilege escalation rather than an urgent remote threat; a vendor patch is available.
Heap-based buffer overflow in the Windows Win32 Kernel Subsystem allows an authenticated local attacker holding only standard user rights to corrupt kernel heap memory and elevate to full SYSTEM-level privileges on unpatched Windows hosts. The vulnerability is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) and affects a very broad install base, spanning Windows 10 1607 through 22H2, Windows 11 23H2 through 26H2, and Windows Server 2016 through 2025, so it functions as a reliable post-compromise escalation primitive rather than an initial-access emergency. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records Exploitation: none, and the CVE is not listed in KEV; Microsoft has released vendor patches with fixed servicing builds for every affected branch.
Local privilege escalation in the Microsoft Windows Search Component lets an attacker who already holds valid low-privilege credentials on an affected Windows host free an object and then reallocate it under their control, corrupting memory inside the component's elevated process. Impacted builds are Windows 11 24H2, 25H2, 26H1 and 26H2 alongside Windows Server 2025 (including Server Core installations) at versions below the fixed build numbers published by the vendor. No public exploit code identified at time of analysis and CISA's SSVC assessment records exploitation as none with the flaw rated non-automatable, but the vendor has shipped a patch and the technical impact is assessed as total (high confidentiality, integrity and availability loss).
Local privilege escalation in the Windows Kernel allows a low-privileged, authenticated attacker who already holds code execution on a target host to trigger a heap-based buffer overflow (CWE-122) and elevate to SYSTEM-level privileges. The vulnerability is strictly local (AV:L) with low privileges required (PR:L) and no user interaction (UI:N), so it provides no remote or network path and is only useful as a post-compromise escalation step rather than an initial access vector. There is no public exploit identified at time of analysis, and CISA's SSVC decision framework rates exploitation as 'none' with 'Automatable: no', because the attacker must already have a local foothold; Microsoft has published patched builds for the affected Windows 11 and Windows Server releases.
Local privilege escalation in Microsoft's Windows Client for NFS allows an authenticated low-privileged attacker who already has code execution on a host to elevate to higher privileges (assessed CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 7.8). Exploitation requires the optional 'Client for NFS' feature to be installed and reachable from the attacker's context, so default installations without that component are not affected, and there is no remote or network-facing attack path. CISA's SSVC assessment records exploitation as 'none' and no public exploit code has been identified at time of analysis; Microsoft has released fixes via its update guide (MSRC advisory for CVE-2026-70113), and the issue is tracked as CWE-190 integer overflow or wraparound.
Heap-based buffer overflow in the Microsoft Windows Storage Spaces driver (Spaceport.sys) allows an authenticated, low-privileged local user to execute code in kernel context and elevate privileges, carrying a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attacker must already hold a session on the target host, so this is best treated as a post-compromise privilege-escalation step rather than a remote entry point, and no user interaction is required beyond the existing local session. Vendor-released patches exist for all affected Windows 10, Windows 11 and Windows Server builds; no public exploit code has been identified at time of analysis and CISA's SSVC assessment records exploitation as "none". Compared with network-facing, pre-authentication bugs this rates as a credible but not emergency-tier priority: patch it on a normal cycle, but prioritize systems where untrusted or low-privileged users can obtain local interactive sessions.
Elevation of privilege in the Microsoft Windows Kernel lets an unauthenticated, remote attacker who can reach the affected kernel code path corrupt or redirect kernel memory and gain SYSTEM-level control of the target host. All currently supported Windows client and server families are in scope - Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025, including Server Core installations - and the assessment vector (AV:N/AC:H/PR:N/UI:N, C:H/I:H/A:H, base 8.1) confirms no credentials or user interaction are needed. The decisive limitation is attack complexity: the attacker must control or influence an untrusted pointer and win a precise kernel memory-layout or timing condition, so this is not a single-shot request. Microsoft has published a fix and there is confirmed vendor patch availability, but no CISA KEV listing and no public exploit code identified at time of analysis; the practical verdict is a genuine high-priority patching candidate rather than a drop-everything emergency.
Local privilege escalation in the Microsoft PostScript Printer Driver allows a low-privileged user on an affected Windows host to gain elevated code execution by having attacker-controlled PostScript/print-driver data processed on the machine, with the root cause classified as a CWE-121 stack-based buffer overflow and a CVSS base score of 7.8. The vector (AV:L/AC:L/PR:N/UI:R) shows no privileges are required prior to exploitation (PR:N) but local presence is mandatory and the victim must be induced to trigger processing of the malicious data (UI:R); CISA's SSVC assessment records Exploitation=none and Automatable=no, and no public exploit code has been identified at time of analysis. This is a credible but context-dependent post-compromise escalation step rather than a mass-exploitation emergency, and a vendor patch is available.
A heap-based buffer overflow (CWE-122) in the Microsoft PostScript Printer Driver lets a local attacker who persuades a victim to process a crafted PostScript print job or document elevate privileges on affected Windows client and server releases. The flaw requires local access (AV:L) and user interaction (UI:R) but no prior privileges (PR:N), so it is a targeted rather than opportunistic local privilege-escalation vector; CISA SSVC rates it non-automatable with no observed exploitation, and no public exploit code has been identified at time of analysis. Vendor patches are available and, per the assessed impact (C:H/I:H/A:H), successful exploitation gives full code execution in the driver's higher-privileged context.
Heap-based buffer overflow in the Windows Win32 kernel subsystem lets a locally authenticated low-privilege attacker escalate to full system privileges on an affected host. Every supported Windows build in the EUVD-listed ranges is exposed by default - Windows 10 21H2 and 22H2, Windows 11 23H2 through 26H2 (including 26H1), and Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025 in both full and Server Core installations - until the corresponding cumulative update is applied; CVSS 3.1 is 7.8 (AV:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so impact on confidentiality, integrity and availability is total once the primitive is triggered. Microsoft has published fixes in its update guide, and no public exploit code or active exploitation has been identified at time of analysis (CISA SSVC exploitation: none). The practical barrier is that the attacker must already hold local code execution on the target, making this a post-compromise privilege-escalation step rather than an initial-access vector.
Heap-based buffer overflow in the Windows kernel (CVE-2026-70106) allows an attacker who already holds low-privileged local code execution to elevate privileges on the affected host, scoring 7.8 under CVSS v3.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exposure is broad across build numbers - Windows 10, Windows 11 and Windows Server 2012 through 2025, including Server Core - but the attack is gated behind an existing local foothold, so it is a post-compromise escalation primitive rather than a remotely reachable one. Microsoft has released fixes through the MSRC update guide, and no public exploit code or confirmed active exploitation was identified at time of analysis (CISA SSVC exploitation: none).
Local privilege escalation in the Windows Win32 Kernel Subsystem lets an attacker who already holds low-privileged, authenticated code execution on a Windows host raise their privileges to kernel level. The flaw is an untrusted pointer dereference (CWE-822) in the kernel that can be triggered with low attack complexity and no user interaction, giving high impact to confidentiality, integrity, and availability (CVSS 3.1 7.8, AV:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified and CISA's SSVC assessment records exploitation as none and automatable as no, so this is a credible but not emergency-level priority; the main constraint on attackers is the need for a pre-existing local foothold on an unpatched build.
Heap-based buffer overflow in Microsoft Windows Error Reporting (WER) lets a locally authenticated attacker holding only low-level privileges elevate their privileges on the host, with full confidentiality, integrity and availability impact (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No user interaction or non-default configuration is required because WER is a built-in subsystem present across every affected Windows 10, Windows 11 and Windows Server 2016-2025 SKU, but the flaw is not remotely exploitable: the attacker must already be able to run code locally under a valid low-privilege account. There is no confirmed active exploitation (the CVE is not in CISA KEV) and no public exploit code identified at time of analysis; Microsoft has published a fix and an advisory entry for the issue, so affected builds below the fixed thresholds should be updated.
Local privilege escalation in the Microsoft Windows Storage Spaces driver (Spaceport.sys) lets an authenticated, low-privileged attacker who already has code execution on a host corrupt kernel memory and obtain SYSTEM-level rights. The defect is a use-after-free (CWE-416) that is locally reachable with low attack complexity and no user interaction, and it affects Windows 10, Windows 11 and Windows Server builds below the fixed versions enumerated in the vendor update. No public exploit code has been identified and CISA's SSVC decision data records no exploitation activity, so this is a genuine but second-tier patching priority relative to any actively exploited issue in the same release cycle.
Heap-based buffer overflow in the Windows iSCSI Initiator component allows a remote unauthenticated attacker to execute arbitrary code on affected Windows 10, Windows 11, and Windows Server 2012 through 2025 systems, provided the target actually uses iSCSI and a user or administrator initiates or accepts a connection to an attacker-controlled iSCSI target (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.5). The user-interaction requirement and High attack complexity - the attacker must also satisfy memory-layout or timing conditions to convert the overflow into reliable code execution - sharply limit the practical attack surface to environments that deploy iSCSI storage. Vendor-released patches are available from Microsoft, CISA's SSVC decision framework rates exploitation as none and automatable as no, and no public exploit identified at time of analysis.
Local privilege escalation in the Windows Rich Text Edit Control (the riched20/msftedit engine used by WordPad, Outlook, and many applications that render Rich Text Format content) lets an attacker who already holds authenticated low-privileged access on a Windows host trigger a heap-based buffer overflow and obtain higher-integrity code execution. Exploitation requires the attacker to invoke the control with attacker-controlled rich-text content (CVSS PR:L, UI:N), so it is a post-compromise escalation primitive rather than a remote or unauthenticated path; SSVC rates the technical impact as total but flags the issue as not automatable, meaning reliable mass exploitation is unlikely, and no public exploit was identified at time of analysis. Microsoft has published a vendor fix, so the residual risk is concentrated on unpatched Windows 10, Windows 11, and Windows Server builds where a low-privileged foothold already exists.
Local privilege escalation in the Microsoft PostScript Printer Driver allows an attacker who gets a victim to open or print a crafted PostScript payload to trigger a heap-based buffer overflow (CWE-122) and execute code in the context of the affected Windows printing component. The flaw affects a broad range of Windows client and server builds - including Windows 10/11 and Windows Server 2012 through 2025 - that have not been updated to their fixed build revision. Per the CVSS vector the attacker needs no pre-existing account (PR:N), but exploitation is local (AV:L) and requires user interaction (UI:R), a crafted document must be processed on the target, and no public exploit code or active exploitation was identified at time of analysis (CISA SSVC: Exploitation = none, Automatable = no).
Heap-based buffer overflow in Microsoft Windows GDI (CWE-122) lets remote attackers achieve code execution on a fully updated-adjacent target by convincing a user to open or preview a maliciously crafted image or document that is parsed through the Windows Graphics Device Interface; the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (8.8) indicates no authentication is needed but that the victim must interact with the attacker-supplied file. Code execution occurs in the security context of the user who opened the file, so the impact is bounded by that user's privileges and no scope change occurs. No public exploit code has been identified at time of analysis and the CISA SSVC decision framework records Exploitation: none with Automatable: no, while Technical Impact is rated total; there is no KEV listing, so this is a high-priority patching item rather than an emergency. Microsoft has published fixed builds covering Windows 10, Windows 11 and Windows Server 2012 through 2025.
Local privilege escalation in Microsoft's Windows Search Component lets an authenticated attacker who already holds a low-privileged session on a Windows host trigger a use-after-free and elevate to a more privileged security context on the same machine. Exploitation is constrained by a high attack complexity rating (AC:H), reflecting a race/timing condition on the freed object that must be won reliably, and the vector (AV:L/PR:L/UI:N) confirms the attacker must already be logged in locally with low privileges; there is no remote attack surface and no victim interaction required. Patches are available from Microsoft (fixed builds such as Windows 11 24H2 10.0.26100.9711 or later), CISA's SSVC assessment records exploitation as none and the issue as not automatable, and no public exploit code has been identified at time of analysis.
Local privilege escalation in the Windows Win32 Kernel Subsystem lets an attacker who already holds low-privileged, authenticated local access on a vulnerable Windows host corrupt kernel memory and elevate to higher privilege, including SYSTEM-level execution. Only specific builds are exposed: Windows 11 24H2, 25H2, 26H1 and 26H2, plus Windows Server 2025 (including Server Core), at build levels below the vendor's fixed releases. Exploitation is constrained by high attack complexity - the use-after-free must be won as a race/timing condition to reclaim the freed Win32 kernel object before it is reused, which limits reliability and makes the flaw non-automatable per CISA SSVC; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (KEV), though the high confidentiality, integrity and availability impact and full technical impact score make timely patching important.
Privilege elevation on unpatched Windows hosts is possible through a heap-based buffer overflow (CWE-122) in the Client-Side Caching (CSC) / Offline Files service, which caches content fetched from SMB network shares. The assessed vector (AV:N/AC:L/PR:N/UI:R) describes an unauthenticated remote attacker, but success hinges on a victim interacting - typically by connecting to or accessing an attacker-controlled share so CSC parses a crafted response and overflows a heap buffer - which is consistent with SSVC rating automatic exploitation as 'no' and with the SSVC exploitation signal of 'none'. Microsoft has released patches for every affected build, and no public exploit code has been identified at time of analysis, so this is a serious but not emergency-grade issue demanding prompt, scheduled patching rather than crisis response.
Local privilege escalation to SYSTEM in the Windows Win32k kernel subsystem affects Windows 10, Windows 11, and Windows Server releases, allowing an authenticated low-privileged attacker already executing code on the host to exploit a use-after-free (CWE-416) condition and gain full kernel-level control (CVSS 3.1 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). The high attack complexity (AC:H) reflects the need to reliably win a race or groom the kernel heap, and there is no remote or network vector, so multi-user, RDP/terminal-server, and kiosk systems are the most relevant risk surface. No public exploit code or active exploitation has been identified at time of analysis.
Integer underflow in the Windows Kerberos authentication component allows a locally authenticated attacker to elevate privileges on an affected host, giving full control over confidentiality, integrity, and availability of the machine. Exploitation requires a prior foothold: the attacker must already hold a valid low-privileged local account (PR:L, AV:L), and no user interaction is needed once that access exists; the flaw is not remotely reachable and SSVC rates it non-automatable, so it cannot be driven at mass or wormable scale. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV), but a vendor patch is available from Microsoft and should be applied to the extensive list of affected Windows 10, Windows 11, and Windows Server builds.
Memory corruption in the libarchive component bundled with Windows (the library behind tar.exe/bsdtar) lets a remote, unauthenticated attacker execute code on affected hosts by having them process a maliciously crafted archive. The root cause is a double free (CWE-415) during archive parsing that corrupts the heap, and because reliably converting that corruption into code execution requires precise heap grooming, Microsoft and our own assessment both rate attack complexity as High despite a CVSS base score of 8.1. No public exploit code has been identified at time of analysis, CISA's SSVC decision framework records exploitation as none and automatable as no, and vendor patches are already available for every affected Windows 10, Windows 11 and Windows Server branch, so this is a serious-but-not-emergency issue that should be closed on a normal patch cadence. One caveat: Microsoft's vector lists UI:N (no user interaction) while our independent assessment uses UI:R, since in interactive deployments a user or application typically has to initiate extraction of the hostile archive - an unattended/service context is where the impact is highest.
Local privilege escalation in the Microsoft Windows Win32 kernel subsystem allows an attacker who already holds low-privilege local access on a Windows host to corrupt heap memory and gain SYSTEM-level code execution. The flaw is a heap-based buffer overflow (CWE-122) rated CVSS 7.8 with a vector of AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning the attacker must be authenticated locally (PR:L, AV:L) and needs to run a crafted program that reaches the vulnerable kernel code path, with no user interaction required. There is no public exploit identified at time of analysis, CISA's SSVC assessment records Exploitation=none and Automatable=no, and vendor-released patches are available for all affected Windows client and server builds.
Local privilege escalation in Microsoft Windows OLE allows an authenticated attacker who already holds a low-privileged foothold on a host to corrupt heap memory through crafted OLE object handling and execute code at a higher integrity level, matching the assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8). Scope is limited to unpatched Windows 10, Windows 11 and Windows Server 2012 through 2025 builds listed by EUVD; because the vector is local-only with PR:L, the flaw is not remotely reachable and cannot be triggered against a default configuration by an outside party. CISA SSVC rates exploitation as "none" and automatable as "no", there is no public exploit identified at time of analysis, and Microsoft has shipped fixes via its Update Guide, making this a credible but not emergency-level priority.
Local privilege escalation in the Windows Update Service allows an attacker who already possesses valid low-privileged local access on an affected Windows host to elevate to a higher-integrity context (including SYSTEM) by triggering a use-after-free. The attack is entirely local - there is no network-facing path - and the assessed vector (AV:L/AC:H/PR:L/UI:N) means successful exploitation depends on winning a race/timing window inherent to the memory-reuse condition, so reliable elevation may require multiple attempts and is not a deterministic one-shot. Affected unpatched builds span Windows 10 21H2/22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2019/2022/2025 (Server Core included); no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, making this a legitimate but moderate-priority LPE rather than an urgent, broadly exploited threat.
Heap-based memory corruption in the Windows NetBIOS component lets an authenticated local attacker with only low-privileged code execution elevate to SYSTEM on unpatched hosts. Exploitation requires an existing foothold - a valid local account and the ability to run code on the target - so this is a post-compromise escalation primitive, not a remote or initial-access vector; no user interaction is required (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8). Microsoft has released fixes and CISA's SSVC assessment rates exploitation as 'none' and the issue as non-automatable, so despite a total technical impact this rates as a genuine but not emergency-tier priority; no public exploit code was identified at time of analysis.
Authenticated local code execution in Windows PowerShell affects Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2) and Windows Server 2022/2025, where a heap buffer overflow triggered by crafted input lets a low-privilege local user run code at the level of the PowerShell process. CVSS 3.1 rates it 7.8 (AV:L/AC:L/PR:L/UI:N, high confidentiality, integrity and availability impact), and because the vector requires an existing local interactive session, the practical exposure is privilege escalation or post-foothold activity on shared hosts rather than a remote or unauthenticated attack. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records exploitation as 'none' and automatable as 'no', and Microsoft has released fixed builds through the MSRC update guide.
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.
A heap-based buffer overflow in the Windows Resilient File System (ReFS) driver (refs.sys) allows a locally authenticated, low-privileged attacker to corrupt kernel heap memory and elevate privileges to SYSTEM on affected Windows 10, Windows 11, and Windows Server builds. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and requires the attacker to already have a foothold on the host plus the ability to feed attacker-controlled input through the ReFS code path, which in practice means a ReFS-formatted volume must be present or mounted for the driver to process that input. Vendor patches are available per the Microsoft advisory, and no public exploit code has been identified at time of analysis (SSVC: Exploitation none, Automatable no); CISA's SSVC framing rates technical impact as total if successfully triggered, but the local-only, authenticated prerequisite and the non-default status of ReFS keep real-world urgency moderate.
Local privilege escalation in Windows Work Folders allows an attacker who already holds authenticated, low-privileged access on an affected Windows 10, Windows 11, or Windows Server host to trigger a use-after-free in the Work Folders code path, corrupting memory and potentially executing code with elevated privileges. The independently assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0) confirms this is a post-compromise escalation step that requires an existing local foothold and a reliably won race/timing window, with no user interaction; there is no public exploit identified at time of analysis and CISA's SSVC assessment records exploitation as none and automatable as no. Microsoft has released fixed builds through the MSRC update guide, so the primary risk is to unpatched hosts where the Work Folders feature is present and in use.
Remote code execution in the Microsoft Windows iSCSI Initiator component (reported against Windows releases carrying the affected MSiSCSI/iSCSI code path) allows an unauthenticated, remote attacker to corrupt heap memory and execute arbitrary code in the context of the iSCSI service by driving a crafted iSCSI protocol exchange against the target. The flaw is a memory-safety defect (reported as a use-after-free, with vendor metadata also flagging buffer/heap overflow and denial-of-service characteristics) reachable from CVSS vector AV:N/AC:H/PR:N/UI:N, so no credentials or user interaction are needed and impact is scored C:H/I:H/A:H - full confidentiality, integrity and availability loss on the host. Exploitation is gated by prerequisites rather than by authentication: the victim host must have the iSCSI Initiator running and must establish a session with an attacker-controlled or spoofed iSCSI target, and the AC:H rating reflects a race/timing condition (or protocol state dependency) the attacker must win reliably. No public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis, so this should be prioritized on exposure and asset criticality rather than on observed in-the-wild activity.
Heap corruption in the Microsoft Windows iSCSI service lets an unauthenticated remote attacker crash or destabilize the service, yielding a denial-of-service condition on any host that has the iSCSI listener enabled and network-reachable. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms network reachability with no credentials, no user interaction, and no non-default configuration beyond the service being turned on, and the impact is confined to availability with no data disclosure or modification. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS or CISA KEV signal was supplied; exposure is therefore driven primarily by deployment, since hosts that do not run the iSCSI service or that firewall its port are not reachable.
Local privilege escalation in Microsoft's Windows Subsystem for Linux (WSL) allows an authenticated low-privileged user with an existing local foothold to corrupt heap memory in the host-side WSL components and cross a security boundary to gain elevated code execution, rated CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-122). The attack is entirely local - there is no network vector - and it requires the optional WSL feature to already be installed and enabled on an affected Windows 10, Windows 11 or Windows Server build, which meaningfully limits the exposed population since WSL is not present by default. Microsoft has published a fix through the MSRC update guide and there is no public exploit identified at time of analysis; CISA's SSVC assessment records exploitation as none and automatable as no.
Use-after-free in Windows Secure Kernel Mode allows an authenticated attacker running code locally on the target with low/standard-user privileges to escalate to higher privilege levels on affected Windows 10, Windows 11 and Windows Server 2019-2025 builds that are below their patched versions. The flaw is rated CVSS 7.0 (HIGH); no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and exploitation is gated by high attack complexity because a reliable UAF typically requires winning a timing race or precisely grooming Secure Kernel memory. Microsoft has released vendor patches - applying the fixed builds removes the condition entirely.
Remote unauthenticated code execution affects Microsoft Internet Information Services (IIS) on Windows: a stack-based buffer overflow in a request-handling parsing path is reachable over the network by anyone who can send crafted input to a running IIS instance. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicates no authentication, no user interaction, and no prior privileges are needed, and a successful exploit yields full loss of confidentiality, integrity, and availability on the host. No public exploit code was identified at time of analysis and there is no CISA KEV listing, but the combination of low attack complexity and unauthenticated network reachability makes this a high-priority item for any internet-facing IIS deployment; version and build specifics must be confirmed from Microsoft's advisory, since no CPE or version detail is provided in the available intelligence.
Local privilege escalation in Microsoft Windows Hyper-V lets an authenticated, low-privileged attacker who already has code execution on a host with the Hyper-V role enabled trigger a use-after-free in a Hyper-V component and gain SYSTEM-level code execution (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U with C:H/I:H/A:H). Affected builds span Windows 10 1809/21H2/22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2019, 2022, and 2025 including Server Core installations; no public exploit code has been identified at time of analysis and CISA SSVC records exploitation as none with Automatable: no, so risk is concentrated on multi-tenant, shared, or virtualization hosts where untrusted low-privilege principals already run. Microsoft has released fixes through the standard Windows cumulative update channel (MSRC advisory CVE-2026-70023, mirrored in ENISA EUVD-2026-100338), and administrators of Hyper-V hosts should treat this as a priority local escalation patch rather than a remote emergency.
Local privilege escalation in Windows Direct Composition (DComp) lets an attacker who already has low-privileged code execution on an affected Windows 11 or Windows Server host escalate to SYSTEM-level privileges. The flaw is a use-after-free (CWE-416) that requires winning a heap-grooming race window, so it is rated high complexity (AC:H) and carries a CVSS of 7.0; exploitation is local and the attacker must be authenticated (PR:L, AV:L) with no user interaction needed (UI:N). Microsoft has released fixes for every affected branch, and there is no public exploit identified at time of analysis - CISA's SSVC assessment records exploitation as "none," making this a moderate-priority patch item rather than an emergency.
Local privilege escalation in the Windows Local Security Authority Subsystem Service (LSASS) allows an authenticated attacker with an existing low-privileged foothold on a host to corrupt heap memory inside the LSASS process and elevate privileges to the level LSASS runs at (SYSTEM). The flaw carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation is local, low-complexity, requires no user interaction, and is confined to the same security scope, so it is a post-compromise escalation step rather than an initial access vector. At time of analysis there is no public exploit identified, CISA's SSVC assessment records Exploitation: none, and the issue is not listed in KEV; a vendor patch is available, so the practical priority is routine patch-cycle remediation rather than emergency response.
Code execution in Windows Cryptographic Services is possible when an authenticated attacker with valid low-privilege credentials and network reachability to the affected host wins a memory-lifecycle race in a freed object (use-after-free). Successful exploitation yields high confidentiality and integrity impact, but the high attack complexity (AC:H) means it depends on non-deterministic heap timing rather than a deterministic trigger, and the CVSS vector requires PR:L, so unauthenticated remote exploitation is not described. No public exploit has been identified at time of analysis, CISA SSVC records Exploitation=none and Automatable=no, and vendor patches are already available for every listed Windows client and server build.
Remote code execution in the Windows iSCSI initiator stack (CVE-2026-70013) allows a network-adjacent attacker to execute arbitrary code with high confidentiality, integrity and availability impact. Affected are the Windows iSCSI components shipped across Windows 10, Windows 11 (23H2 through 26H2) and Windows Server 2012 through Server 2025, including Server Core installations, with vendor fixes now published. Exploitation requires an active iSCSI session - typically a target the attacker controls or can inject responses into - and, because the flaw is a use-after-free race (CWE-416, AC:H), success depends on winning a memory-reuse timing window rather than issuing a single deterministic request; no public exploit code has been identified at time of analysis and CISA's SSVC assessment records Exploitation: none, so this is a serious-but-not-emergency priority rather than an active incident.
Use-after-free in the Windows Remote Desktop Client lets an unauthenticated attacker execute arbitrary code on a connecting client by luring a user into initiating an RDP session to an attacker-controlled or compromised server. The vector is network-reachable with no privileges required (PR:N), but practical exploitation depends on the victim starting the outbound connection (UI:R) and on the attacker winning a specific memory-state or timing condition (AC:H), which is consistent with CISA's SSVC rating of non-automatable and no observed exploitation. No public exploit code has been identified at time of analysis and Microsoft has published fixed builds covering all affected Windows 10, Windows 11 and Windows Server platforms; because the trigger is client-initiated rather than a passive listening service, the realistic delivery paths are malicious .rdp files, crafted links, or a hijacked RDP endpoint.
Local privilege escalation in Microsoft Windows NTFS (CVE-2026-70010) allows an authenticated, low-privileged user to corrupt kernel heap memory via crafted NTFS filesystem operations and elevate to SYSTEM. The flaw is a heap-based buffer overflow (CWE-122) in the in-kernel NTFS driver, rated CVSS 7.8 (HIGH) with the vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning the attacker must already hold a local foothold on the host but needs no user interaction and faces low attack complexity. Exploitation is not remotely reachable over the network, no public exploit code has been identified at time of analysis, and CISA's SSVC assessment records exploitation as 'none'; patch availability is confirmed through the Microsoft MSRC update guide.
Local privilege escalation in the Windows IP Over USB Service (IpOverUsbSvc) allows an attacker who already holds a low-privileged, authenticated session on a Windows host to overflow an integer value and consequently gain SYSTEM-level code execution, with high impact to confidentiality, integrity, and availability. Affected builds span Windows 10 (21H2/22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), and Windows Server 2022/2025 according to the EUVD version ranges, although the vulnerable service ships with developer/SDK and device-debugging tooling rather than being enabled on default installations. Exploitation requires local access and the service to be installed and running, so the practical fleet at risk is developer and debugging workstations; there is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), and a vendor patch is available.
A use-after-free (CWE-416) in the Microsoft Windows Remote Desktop Client allows an unauthenticated attacker to execute code on a victim's machine when that user initiates an outbound connection to an attacker-controlled RDP server. The flaw is client-side rather than a remotely reachable service bug: the attacker must control the server endpoint and also win a race condition inherent to the use-after-free (AC:H), while the victim must open a crafted .rdp file or otherwise accept the connection (UI:R), which is why the CVSS 3.1 base score sits at 7.5 even though a successful exploit yields full confidentiality, integrity and availability impact. Vendor-released patches are available, no public exploit code has been identified at time of analysis, and CISA's SSVC assessment records exploitation as none and automatable as no, so this is a moderate-priority issue rather than an urgent one.
Use-after-free in the Windows Remote Desktop Client allows a malicious or compromised RDP server to execute code on a Windows machine that connects to it, affecting builds across Windows 10, Windows 11 (23H2 through 26H2), and Windows Server 2012 through 2025. Exploitation is client-side: an attacker must induce a victim to open a crafted .rdp file or otherwise initiate an outbound RDP session, and with AC:H plus mandatory UI:R, reliable code execution depends on winning a heap race rather than a single deterministic response, so mass opportunistic exploitation is unlikely while targeted social-engineering delivery is plausible. No public exploit identified at time of analysis; CISA's SSVC rates exploitation as none and automation as not automatable, and the PR:N vector means the victim need not authenticate to the attacker.
A use-after-free (CWE-416) in the Windows Remote Desktop Client lets an attacker who controls or compromises an RDP server execute arbitrary code on the connecting client, as described in Microsoft's MSRC advisory for CVE-2026-69998. Exploitation is not passive: the victim must actively initiate an RDP session to the hostile endpoint (UI:R), and the unauthenticated attacker (PR:N) must still win a memory-management race or reliably groom the freed heap object to convert the corruption into code execution (AC:H), giving a CVSS 3.1 base score of 7.5. All supported Windows client and server builds below the patched build levels are affected; there is no public exploit identified at time of analysis, no confirmed active exploitation (CISA KEV), and CISA SSVC records exploitation as none and automatable as no, so the practical risk is driven by social engineering of an outbound RDP connection plus patch lag.
Use-after-free memory corruption in the Microsoft Windows Remote Desktop Client (mstsc.exe) can let an unauthenticated remote attacker execute arbitrary code on a vulnerable client, but only after the victim initiates an outbound RDP connection to an attacker-controlled, compromised, or spoofed RDP server. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.5) confirms the mandatory user interaction and high attack complexity, and CISA's SSVC assessment records exploitation as 'none' and automatable as 'no'; no public exploit code has been identified at time of analysis. Microsoft has released fixes via the MSRC update guide, so the practical risk is moderate and concentrated on hosts that routinely open RDP sessions to untrusted or third-party endpoints.
Use-after-free in the Windows Remote Desktop Client allows a malicious or compromised RDP server to corrupt memory and execute code on the machine that connects to it (CVSS 7.5, C:H/I:H/A:H, SSVC Technical Impact 'total'). The attack is client-initiated and outbound - it requires the victim to establish an RDP session to the hostile endpoint (UI:R) and a favorable memory/race condition to be won (AC:H) - so it does not target a listening RDP service, and no privileges are required on the client (PR:N, unauthenticated). Current intelligence indicates no public exploit code and no confirmed active exploitation (CISA SSVC Exploitation: none; Automatable: no), while Microsoft has released a vendor patch, making this a high-impact-but-not-urgent issue at time of analysis.
Code execution in the Windows Remote Desktop Client (mstsc) is possible when a user initiates an outbound RDP session to a malicious or attacker-controlled server, triggering a use-after-free that can be leveraged for arbitrary code in the client's context. Affected are unpatched Windows client and server builds below their fixed versions - including Windows 10 1607 through 22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2012/2012 R2/2016/2019/2022/2025 - while the attacker requires no credentials (PR:N) and the flaw cannot be triggered against a listening host without the victim's outbound connection (UI:R). Exploitation is rated high-complexity (AC:H) because the attacker must reliably win the heap/timing-dependent memory corruption condition; there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), and Microsoft has released patched builds.
Use-after-free memory corruption in the Windows Remote Desktop Client allows an unauthenticated remote attacker to execute code in the context of the connecting user, but only after the victim initiates an outbound RDP session to an attacker-controlled or compromised server. Microsoft rates the issue 7.5 (High) under CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, reflecting a total loss of confidentiality, integrity, and availability that is tempered by high attack complexity and mandatory user interaction. CISA's SSVC assessment records exploitation as 'none' and no public exploit identified at time of analysis; Microsoft has released fixed builds through its update guide.
Remote code execution in Windows Remote Desktop Services is possible through a use-after-free (CWE-416) in the RDP component, rated CVSS 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H). An unauthenticated remote attacker can achieve high confidentiality, integrity, and availability impact, but exploitation is not reliable: the attacker must satisfy a race or heap-grooming condition (AC:H), and a victim must initiate or accept a Remote Desktop connection to an attacker-controlled endpoint (UI:R). No public exploit code is identified at time of analysis, CISA SSVC records exploitation as none, and Microsoft has released patches; hosts without the Remote Desktop/RDS role enabled are not exposed, so risk is concentrated on internet- or untrusted-network-facing RDP deployments.
Remote code execution in Microsoft's Windows Remote Desktop Client stems from a use-after-free (CWE-416) triggered when the client processes crafted data supplied by an RDP server. An unauthenticated attacker can exploit this over a network only by inducing a user to connect to an attacker-controlled or compromised RDP server - for example by opening a malicious .rdp file or link - after which heap corruption can lead to code execution in the context of the client. The CVSS 3.1 base score is 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H), reflecting required user interaction and high attack complexity; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', no public exploit code has been identified at time of analysis, and the vulnerability has not been confirmed actively exploited (CISA KEV). Vendor patches are available, so the practical risk is concentrated in unpatched Windows clients exposed to untrusted RDP endpoints.
Remote code execution affects the Windows Remote Desktop Client (mstsc) across a wide range of supported desktop and server builds, allowing an attacker who controls or manipulates an RDP endpoint to execute code in the context of the connecting user. The flaw is a use-after-free (CWE-416) rated CVSS 7.5; exploitation requires the victim to actively initiate an RDP session outward to the hostile server (UI:R), and high attack complexity (AC:H) reflects dependence on heap/race conditions rather than a deterministic trigger - no authentication is required of the attacker (PR:N). No public exploit code has been identified at time of analysis and CISA's SSVC records Exploitation=none with no KEV listing, so risk is driven by the breadth of affected Windows builds and the total technical impact should the memory-corruption primitive be reliably converted into code execution.
Outbound RDP sessions from the Windows Remote Desktop Client can be turned against the client itself: when a user connects to an attacker-controlled, compromised, or man-in-the-middle'd RDP server, crafted response data triggers a use-after-free (CWE-416) that can lead to code execution on the victim's machine, with total technical impact if the memory corruption is reliably steered. The attacker needs no credentials on the client (PR:N) and can operate remotely over the network (AV:N), but exploitation is gated by mandatory user interaction (the user must actively initiate the session, UI:R) and high attack complexity (AC:H) reflecting the precision required to trigger and control the freed allocation. Microsoft rates this CVSS 7.5 and has released vendor patches; there is no public exploit identified at time of analysis and no evidence of exploitation - CISA's SSVC assessment records Exploitation: none and Automatable: no.
A use-after-free (CWE-416) in the Windows Remote Desktop Client (mstsc.exe / RDP client stack) allows remote code execution in the security context of the connecting user when that user establishes an outbound RDP session to an attacker-controlled or compromised RDP server. Exploitation is unauthenticated with respect to the client (CVSS 3.1 PR:N) but requires user interaction (UI:R) and is rated high attack complexity (AC:H), because the attacker must deliver crafted server-side RDP protocol data and win a race condition over the freed object; the resulting impact is full compromise of confidentiality, integrity and availability within the user's own security scope (S:U, no privilege escalation to SYSTEM). Microsoft has released a vendor patch covering Windows 10, Windows 11 and Windows Server 2012 through 2025, exploitation has not been observed by CISA SSVC assessment (Exploitation: none, Automatable: no), and no public exploit code was identified at the time of analysis.
Heap-based buffer overflow in the Windows Libarchive component - the library Windows uses to extract 7z, rar, tar, cab and similar archive formats - lets a remote attacker execute arbitrary code with the privileges of the user who opens a malicious archive. Because exploitation is delivered over the network (AV:N) with no authentication required (PR:N) but demands that the victim open or process the crafted file (UI:R), the realistic attack path is a phishing email attachment, a web download, or a hosted share rather than anything wormable; CISA's SSVC decision framework reflects this with Exploitation=none and Automatable=no. There is no public exploit identified at time of analysis and vendor patches are available, so the practical priority is patch deployment rather than emergency containment - while noting the CVSS 8.8 score masks that the mandatory user interaction is the single factor keeping risk below critical.
Use-after-free (CWE-416) in the Windows Remote Desktop Client (mstsc) allows remote code execution on a Windows client that connects out to a malicious or compromised RDP server, affecting all supported Windows 10, Windows 11, and Windows Server builds below the fixed patch levels listed in Microsoft's advisory. Exploitation is not opportunistic: it follows a reverse-RDP pattern in which the victim must initiate the session (UI:R) against attacker-controlled server infrastructure, and public exploitation is not confirmed - CISA SSVC records exploitation as 'none' and no public exploit code has been identified at time of analysis. The negotiated CVSS of 7.5 is driven by high attack complexity (AC:H), reflecting the heap-state and timing control needed to win the use-after-free race, while requiring no privileges on the victim (PR:N) and impacting confidentiality, integrity, and availability equally.
Local privilege escalation in Microsoft's Quality Windows Audio/Video Experience (QWAVE) service stems from a use-after-free condition (CWE-416) that can let an already-authenticated local user execute code in the service's more privileged context, with high impact to confidentiality, integrity and availability (C:H/I:H/A:H). Rated CVSS 7.0 with a vector of AV:L/AC:H/PR:L/UI:N/S:U, exploitation requires an attacker who already holds a local account on the host and who can also win a timing or object-lifetime race - CISA's SSVC assessment records Exploitation=none and Automatable=no, and there is no public exploit identified at time of analysis. Microsoft has shipped vendor-released patches for every affected branch, so this is best treated as a moderate-priority post-foothold escalation whose realistic risk is lower than the base score alone suggests, rather than an emergency to be handled outside the normal patch cycle.
Remote code execution in the Microsoft Remote Desktop Client (CWE-416) occurs when a user initiates an RDP connection to an attacker-controlled or compromised server that returns crafted responses, causing the client to reuse a freed memory object. The CVSS vector (AV:N/AC:H/PR:N/UI:R) shows an unauthenticated attacker is required to hold no credentials on the victim host, but must convince the user to start the session and satisfy high-complexity heap-timing conditions for reliable exploitation; impact is confined to the connecting user's security context with no privilege escalation implied. Exploitation only triggers on a client that actively connects outbound, and no public exploit identified at time of analysis.
Heap-based buffer overflow in the Microsoft Streaming Service, a Windows kernel-mode component, allows an attacker who already holds local access and low-privileged code execution on the host to elevate to SYSTEM-level privileges. The flaw is not remotely reachable: exploitation requires direct interaction with the affected kernel driver (AV:L) and a high-complexity trigger condition (AC:H), typically a race or a carefully shaped heap layout, so reliable exploitation is non-trivial even though no victim interaction is needed (UI:N). Per the available intelligence, there is no public exploit code and no KEV confirmation, so exploitation status at time of analysis is: no public exploit identified; the primary defence is prompt application of Microsoft's update from the MSRC advisory.
Local privilege escalation in Microsoft Streaming Service on Windows 10, Windows 11 (21H2 through 26H2) and Windows Server 2012 through 2025 allows an authenticated, low-privilege attacker who already has code execution on the host to exploit an integer wraparound and elevate privileges, with total impact to confidentiality, integrity and availability (CVSS 7.8). The flaw is strictly local - the vector (AV:L/PR:L/UI:N) rules out remote or unauthenticated reach - and SSVC records exploitation as none with automatable set to no, so no public exploit code has been identified at time of analysis. This is a genuine patch-priority issue but not an emergency, and it matters most on multi-user, terminal-server and jump hosts where untrusted users can already run code.
Local code execution and information disclosure on patched-but-not-updated Windows hosts can result from an out-of-bounds read in the Windows Overlay Filter (WOF), a kernel-mode filesystem filter driver that services compressed and overlay file operations. Affected are Windows 10 (1607 through 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), and Windows Server 2012 through 2025 in both full and Server Core installations below the builds listed in the vendor update matrix. Exploitation requires a pre-existing local, authenticated foothold with at least low-level privileges (CVSS:3.1/AV:L/AC:L/PR:L/UI:N) - remote, unauthenticated attack is not possible - and no public exploit code has been identified at time of analysis, with SSVC recording Exploitation=none and Automatable=no, placing this in the post-compromise privilege-escalation and information-leak class rather than a wormable emergency. A vendor patch is available and should be applied through the standard Microsoft monthly servicing channel.
Elevation of privilege in the Windows Overlay Filter (WOF) driver allows an attacker who already holds a low-privileged local foothold on a supported Windows host to run code at SYSTEM level by triggering an integer overflow/wraparound during a filter operation. Exploitation is local-only and requires authenticated code execution at low privilege (CVSS:3.1/AV:L/AC:L/PR:L/UI:N, base 7.8) with no user interaction; CISA's SSVC assessment records Exploitation=none and Automatable=no, so there is no public exploit identified at time of analysis. Vendor patches exist for every affected SKU, which materially lowers residual risk for organizations that have applied current servicing updates.
Local privilege escalation in the Microsoft Windows Overlay Filter (WOF) affects default installations of Windows 10, Windows 11, and Windows Server 2012 through 2025 that have not yet applied the fixed builds listed in the EUVD advisory. An attacker who already holds a low-privileged, authenticated local session (CVSS vector PR:L, AV:L) can trigger a buffer over-read in the filter - tracked as CWE-126 - and, on success, gain high confidentiality, integrity, and availability impact as reported by the assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H score of 7.8. No user interaction is required and there is no remote or network attack vector; exploitation status is neutral (SSVC: Exploitation none, Automatable no), with no public exploit identified at time of analysis. This is a genuine but second-tier priority: the vendor has shipped patches, and the flaw is only reachable from an already-compromised local user context.
Out-of-bounds read in the Windows Overlay Filter (wof.sys), a kernel-mode Windows component enabled by default, allows an authenticated local attacker with an existing low-privileged foothold to elevate privileges on the host (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Because wof.sys loads by default across supported client and server editions, no non-default configuration is required to reach the vulnerable code; the primary gating factor is the prerequisite of local code execution, and no public exploit has been identified at time of analysis, with CISA SSVC rating exploitation as none and the attack as not automatable. Successful exploitation yields total technical impact per SSVC (high confidentiality, integrity and availability impact), consistent with a kernel-level memory-safety primitive being turned into local privilege escalation.
Local privilege escalation in the Windows Overlay Filter (WOF) driver lets an attacker who already holds low-privileged, authenticated local access on an affected Windows host trigger a buffer over-read (CWE-126) that can be leveraged to gain elevated privileges, with high confidentiality, integrity and availability impact, matching the CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is not remotely reachable and cannot be used for initial compromise because it requires an existing foothold on the machine, and CISA's SSVC assessment records no observed exploitation while no public exploit has been identified at time of analysis. Microsoft has shipped vendor patches covering the affected Windows 10, Windows 11 and Windows Server 2012 through 2025 builds, so this is best treated as a credible patch-cycle priority rather than an emergency.
Local privilege escalation in the Windows Client for NFS affects systems where the optional Client for NFS feature has been installed, allowing an attacker who already holds authenticated low-privileged local access to trigger a heap-based buffer overflow (CWE-122) and gain full control of the host at the kernel/SYSTEM level. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation is local, requires low privileges, needs no user interaction, and is confined to the affected machine - a technically complete compromise but not a remotely reachable or self-propagating one. There is no public exploit identified at time of analysis, CISA's SSVC assessment records Exploitation: none and Automatable: no, and the vendor has released patched builds, so this is best treated as a genuine but second-tier local privilege-escalation issue whose real-world exposure is gated by whether the NFS client component is present.
Local privilege escalation in the Windows AppX Deployment Extensions component allows an authenticated, low-privileged attacker who already has code execution or interactive access on a host to elevate to a higher-integrity context, including SYSTEM, because a required authorization check is missing (CWE-862). The flaw carries a CVSS 3.1 base score of 8.8 from the vector AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - the Scope:Changed rating reflects that a successful exploit crosses a privilege boundary, granting high confidentiality, integrity, and availability impact. Every supported Windows client and server release is exposed, and because the component ships in default Windows installations, no unusual configuration is required once the attacker has a foothold; there is no KEV listing and no public exploit identified at time of analysis, though the low attack complexity and absence of user interaction make it an attractive post-compromise escalation primitive. Microsoft has released fixed builds, so this is a genuine prioritization candidate for patch cycles rather than an unmitigable emergency, but the hard prerequisite of existing local access is the main constraint on real-world risk.
Code execution in the Windows Overlay Filter (WOF) driver lets a locally authenticated attacker trigger an out-of-bounds memory read and, per Microsoft's severity rating, achieve code execution with high confidentiality, integrity and availability impact on unpatched machines. The flaw (CVE-2026-69942, CWE-126, CVSS 7.8 / AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) requires a pre-existing local foothold and low-privileged credentials, so it is a post-compromise privilege-escalation issue rather than an initial access vector, affecting Windows 11 23H2, 24H2, 25H2, 26H1 and 26H2 plus Windows Server 2022 and Windows Server 2025 (including Server Core) below their fixed build levels. CISA's SSVC assessment records Exploitation: none and Automatable: no, and no public exploit identified at time of analysis; Microsoft has released a fix, so exposure is confined to systems that have not yet installed the current cumulative update.
Local privilege escalation in the Windows Storage component allows an authenticated, low-privileged attacker to gain full control of a Windows host (C:H/I:H/A:H) by winning a race condition that triggers a use-after-free in the storage stack. Exploitation requires an existing local foothold (AV:L, PR:L) and is timing-dependent and non-deterministic (AC:H, CWE-362), so it is a post-compromise escalation primitive rather than a remotely reachable or mass-exploitable bug. This is a moderate-priority local elevation-of-privilege flaw, not an emergency: no public exploit code and no evidence of active exploitation were identified at time of analysis (SSVC Exploitation=none, Automatable=no), and Microsoft has released a vendor patch.
Local privilege escalation in the Windows Spaceport.sys Storage Spaces kernel driver allows an authenticated attacker who already has the ability to execute code as a low-privileged user on an affected host to gain full SYSTEM-level privileges. An integer overflow/wraparound in the driver's handling of size or index values lets a crafted request corrupt kernel memory, yielding complete loss of confidentiality, integrity, and availability (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). All unpatched Windows 11 releases from 23H2 through 26H2, Windows Server 2022, and Windows Server 2025 (including Server Core) installations with the driver loaded at defaults are in scope, but exploitation is not automatable per SSVC, and no public exploit identified at time of analysis.
Local privilege escalation in the Windows Storage component lets an attacker who already holds a foothold on a Windows host with low-level privileges (PR:L) escalate to full system rights by winning a race condition (CWE-362) in the storage subsystem's handling of a shared resource. The attack is entirely local (AV:L), requires no user interaction, and is assessed at CVSS:3.1 base 7.0 with HIGH attack complexity because the timing window is narrow and non-deterministic, which is why CISA's SSVC rates it non-automatable with no observed exploitation; no public exploit code was identified at time of analysis. Because successful escalation grants high confidentiality, integrity and availability impact on the host, unpatched Windows 10, Windows 11 and Windows Server builds exposed to multi-user or post-compromise scenarios should be prioritized for the vendor patch.
Local privilege escalation in Microsoft's Desktop Window Manager (dwm.exe) allows a low-privileged attacker who already has code execution on a Windows system to bring about a type-confusion condition and obtain elevated rights, scored CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Because DWM is present and running by default in every interactive Windows desktop session, no special feature or non-default configuration is required to reach the vulnerable code; only a locally executed crafted program is needed. This is a post-compromise escalation primitive rather than a remote entry point, no public exploit identified at time of analysis, and Microsoft's MSRC update-guide entry is the authoritative reference for affected builds and the fix.
Remote code execution is possible in the Microsoft PostScript Printer Driver, where a heap-based buffer overflow (CWE-122) lets an unauthenticated attacker who can deliver crafted PostScript print data over the network corrupt heap memory and execute arbitrary code in the context of the Windows Print Spooler. The flaw carries a CVSS 3.1 base score of 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), meaning no authentication and no user interaction are required; every supported Windows client and server release from Windows Server 2012 through Windows 11 26H2 and Windows Server 2025 is affected unless it has been updated to the fixed build listed by Microsoft. Vendor patches are available, and no public exploit code or active exploitation has been identified at time of analysis - SSVC records exploitation as 'none' - so the practical exposure is driven by whether the print/spooler service is reachable from untrusted networks.
Local privilege escalation in the Windows Win32 kernel subsystem allows an authenticated attacker running as a low-privileged user to abuse a use-after-free condition in a kernel object and elevate to full system privileges, with high confidentiality, integrity, and availability impact (CVSS 3.1 base 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). Only specific Windows 11 builds (23H2, 24H2, 25H2, 26H1, 26H2) and Windows Server 2025 (including Server Core) below Microsoft's fixed builds are affected; exploitation is not remote, requires no user interaction, and hinges on winning a timing-dependent race window, which lowers exploit reliability. No public exploit identified at time of analysis, CISA's SSVC assessment records exploitation as 'none' and automatable as 'no', and Microsoft has shipped a vendor patch, so fully updated hosts are not exploitable - the overall priority is moderate rather than emergency.
A heap-based buffer overflow in the Windows Network File System (NFS) Server role lets an attacker who already holds local, low-privileged authenticated access on a Windows host execute code in a higher-privileged context, with high impact to confidentiality, integrity, and availability (CVSS 3.1 base 7.8, AV:L/PR:L/UI:N). Exploitation is constrained by prerequisites: the optional NFS Server / Services for NFS feature must actually be installed and enabled - it is absent from default Windows installations - and the attacker must already be on the box with valid low-privilege credentials; no user interaction is required. Vendor-released patches exist for all listed Windows client and server builds, no public exploit code has been identified at time of analysis, and there is no confirmed active exploitation (CISA KEV), so this is a moderate-to-serious patching priority rather than a top-tier emergency. Defenders should note the scoring discrepancy flagged in the independent assessment: NFS is a network-facing service, yet Microsoft scored the vector as LOCAL - confirm via the MSRC advisory whether any network-adjacent trigger path exists beyond the local vector.
Local privilege escalation in the Windows Update Service allows an authenticated, low-privileged user on Windows 11 (23H2, 24H2, 25H2, 26H1 and 26H2) or Windows Server 2025 to run code as SYSTEM by placing a malicious module in a directory the service searches ahead of the trusted location (CWE-426 untrusted search path, CVSS 7.8, vector CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exploitation is not remote: an attacker must already hold a local authenticated account with write access to a directory in the service's search order, and CISA's SSVC assessment records exploitation as none, automatable as no and technical impact as total, making this a manual post-compromise escalation rather than a self-propagating or wormable issue. No public exploit code was identified at time of analysis, and Microsoft has published fixing updates through its MSRC Update Guide.
Local privilege escalation in the Windows Audio Service lets an attacker who already holds low-privilege code execution on a Windows host trigger a use-after-free (CWE-416) and elevate to a more privileged context. The flaw is rated CVSS 7.0 (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H): it is not remotely reachable, requires an existing foothold and local code execution, and the high attack complexity reflects a race/timing window that must be won, making exploitation non-deterministic. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records exploitation as none and non-automatable, and the issue does not appear in CISA KEV; completely patched builds are available from Microsoft.
Local privilege escalation in the Windows Update Service lets an authenticated attacker with low-level local access (CVSS PR:L/AV:L) corrupt heap memory to gain SYSTEM-level code execution on unpatched Windows client and server builds. The flaw is a heap-based buffer overflow (CWE-122) that requires no user interaction and no special configuration, since the Windows Update Service is enabled by default; exploitation cannot be automated or performed remotely, and no public exploit code or active exploitation has been identified at time of analysis.
Local privilege escalation in Microsoft Windows OLE allows an attacker who already holds low-privileged authenticated access on a host to drive a heap-based buffer overflow by inducing the vulnerable component to process a crafted OLE object, resulting in code execution at a higher integrity level with complete loss of confidentiality, integrity, and availability (CVSS 7.8, CWE-122). The issue spans a wide set of unpatched Windows client and server builds, including Windows 10 21H2/22H2, Windows 11 23H2 through 26H2, and Windows Server 2012, 2012 R2, 2016, 2019, 2022, and 2025; vendor fixes are available and no public exploit code was identified at time of analysis. Because the attack is local (AV:L), requires existing credentials (PR:L), needs no victim interaction (UI:N), and is classified as non-automatable with exploitation 'none' under CISA's SSVC framework, it is a second-tier, post-compromise escalation primitive rather than a remote or wormable threat.
Local privilege escalation in the Microsoft Windows Search component lets an authenticated attacker with a low-privileged local account corrupt memory and potentially execute code at a higher integrity level. The flaw is a use-after-free (CWE-416) rated CVSS 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation is local, requires prior authentication, needs no user interaction, and carries high attack complexity because the attacker must reliably reclaim a freed object. Microsoft has released vendor patches; no public exploit code has been identified, and CISA's SSVC assessment records exploitation as none with the issue not automatable (technical impact: total).
Local privilege escalation in the Windows Event Tracing (ETW) subsystem allows an attacker who already holds low-privileged code execution on a host to raise their privileges, with high confidentiality, integrity and availability impact (CVSS 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). The root cause is a use-after-free (CWE-416) that is only reachable locally and additionally requires winning a timing race, so reliable exploitation is non-trivial; no public exploit identified at time of analysis and the flaw is not listed in CISA KEV, with CISA SSVC scoring exploitation as 'none' and automatable as 'no'. Microsoft has released a vendor patch, and risk is concentrated on multi-user, terminal/RDP, or shared systems where untrusted low-privilege accounts can run code - a moderate, not emergency, priority.
Network denial of service in Windows SMB Server allows unauthenticated remote attackers to make the service allocate resources without throttling, exhausting memory or handles until SMB-dependent services and, potentially, the host become unresponsive. Tracked as CWE-770 and scored 7.5 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H), it affects Windows 10 (1607 through 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1/26H2) and Windows Server 2012 through Server 2025, with impact confined to availability - there is no disclosure or code-execution path. No public exploit has been identified at time of analysis, CISA's SSVC assessment records exploitation as 'none' (automatable: yes, technical impact: partial), and vendor-released patches are available through the Microsoft update guide referenced by the advisory.
Local privilege escalation in the Windows Portable Device File System Driver lets an authenticated, low-privileged attacker who already has code execution on a Windows host trigger a heap-based buffer overflow (CWE-122) and elevate to SYSTEM. The flaw spans an unusually wide set of builds - Windows 10 (1607 through 22H2), Windows 11 (23H2 through 26H2), and Windows Server 2012 through 2025, including Server Core installations - and carries a vendor CVSS of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Microsoft has released fixes, CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', and no public exploit code has been identified at time of analysis; the operative constraint is the required local foothold, which makes this a second-stage escalation primitive rather than an entry point.
Heap-based buffer overflow in Microsoft Windows Media Foundation allows a local attacker to elevate privileges on affected Windows hosts by supplying a crafted media file that the logged-in user opens, previews, or otherwise has parsed by the platform's media pipeline. Successful exploitation is assessed at CVSS 3.1 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, CWE-122), yielding high confidentiality, integrity, and availability impact; because the vector is local with a user-interaction prerequisite, the attacker must first land the file on the target and induce the user to process it, which makes this a credible but interaction-gated escalation path rather than a network-facing exploit. No public exploit code has been identified at time of analysis and the flaw is not confirmed actively exploited (CISA KEV); a vendor patch is available, and fully updated builds (those at or above the version thresholds enumerated in the EUVD affected-version data) are not affected. Despite being an LPE rather than an RCE, the no-privilege prerequisite, low complexity, and full three-property impact keep this a legitimate prioritization candidate in environments where media files are routinely handled.
Memory-safety failure in the Windows Bluetooth Port Driver lets a device within Bluetooth radio range trigger out-of-bounds memory access that can escalate to code execution on unpatched Windows 10, Windows 11, and Windows Server hosts with an active Bluetooth radio. Exploitation requires proximity (adjacent network), the victim's Bluetooth to be enabled and in use, some form of user interaction such as accepting or initiating a Bluetooth connection, and high attack complexity reflecting preconditions outside the attacker's control; authentication is not required (CVSS:3.1/AV:A/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H). Microsoft has shipped fixes, no public exploit code has been identified at time of analysis, CISA's SSVC assessment records exploitation as "none" with the attack assessed as non-automatable, and hosts with Bluetooth disabled are not exposed - making this a moderate rather than top-tier priority despite the 7.1 score and the CVSS "total" technical impact rating on affected devices.
Local privilege escalation in the Microsoft Graphics Component affects multiple Windows client and server builds, allowing a local, authenticated attacker with low privileges (CVSS AV:L/PR:L) to exploit a numeric truncation error and gain High confidentiality, integrity, and availability impact after corrupting heap memory. The vulnerability has a CVSS 3.1 base score of 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), requires no user interaction, and is not a remote entry point; no public exploit was identified at time of analysis, and no EPSS score was provided. A vendor patch is available per Microsoft, so affected organizations should prioritize update deployment on all listed Windows versions and Server Core installations.
Local privilege escalation in the Windows Kernel allows an authenticated low-privilege attacker with existing code execution on a target host to trigger a heap-based buffer overflow and elevate privileges in kernel mode. Affected default installations include Windows 10, Windows 11 21H2 through 26H1, and Windows Server 2019/2022/2025 builds below the vendor-patched build levels. No public exploit identified at time of analysis and CISA SSVC reports no exploitation; a vendor patch is available.
Local privilege escalation in the Windows Audio Service (audiosrv) affects Windows 11 versions 24H2, 25H2, 26H1 and 26H2 as well as Windows Server 2025 (including Server Core), allowing an attacker who already holds a low-privileged foothold on the host to execute code in a more privileged context. Exploitation requires an authenticated local attacker with the ability to interact with the audio service (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H), and the high attack complexity indicates the use-after-free hinges on a race or specific heap/object state that is difficult to trigger reliably; the service runs by default, so every affected build is exposed once a foothold exists. There is no public exploit identified at time of analysis, CISA SSVC records exploitation as none and the issue is not automatable, so this is a genuine but moderate-priority local privilege escalation rather than an urgent remote threat; a vendor patch is available.
Heap-based buffer overflow in the Windows Win32 Kernel Subsystem allows an authenticated local attacker holding only standard user rights to corrupt kernel heap memory and elevate to full SYSTEM-level privileges on unpatched Windows hosts. The vulnerability is strictly local (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8) and affects a very broad install base, spanning Windows 10 1607 through 22H2, Windows 11 23H2 through 26H2, and Windows Server 2016 through 2025, so it functions as a reliable post-compromise escalation primitive rather than an initial-access emergency. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records Exploitation: none, and the CVE is not listed in KEV; Microsoft has released vendor patches with fixed servicing builds for every affected branch.
Local privilege escalation in the Microsoft Windows Search Component lets an attacker who already holds valid low-privilege credentials on an affected Windows host free an object and then reallocate it under their control, corrupting memory inside the component's elevated process. Impacted builds are Windows 11 24H2, 25H2, 26H1 and 26H2 alongside Windows Server 2025 (including Server Core installations) at versions below the fixed build numbers published by the vendor. No public exploit code identified at time of analysis and CISA's SSVC assessment records exploitation as none with the flaw rated non-automatable, but the vendor has shipped a patch and the technical impact is assessed as total (high confidentiality, integrity and availability loss).
Local privilege escalation in the Windows Kernel allows a low-privileged, authenticated attacker who already holds code execution on a target host to trigger a heap-based buffer overflow (CWE-122) and elevate to SYSTEM-level privileges. The vulnerability is strictly local (AV:L) with low privileges required (PR:L) and no user interaction (UI:N), so it provides no remote or network path and is only useful as a post-compromise escalation step rather than an initial access vector. There is no public exploit identified at time of analysis, and CISA's SSVC decision framework rates exploitation as 'none' with 'Automatable: no', because the attacker must already have a local foothold; Microsoft has published patched builds for the affected Windows 11 and Windows Server releases.
Local privilege escalation in Microsoft's Windows Client for NFS allows an authenticated low-privileged attacker who already has code execution on a host to elevate to higher privileges (assessed CVSS 3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, score 7.8). Exploitation requires the optional 'Client for NFS' feature to be installed and reachable from the attacker's context, so default installations without that component are not affected, and there is no remote or network-facing attack path. CISA's SSVC assessment records exploitation as 'none' and no public exploit code has been identified at time of analysis; Microsoft has released fixes via its update guide (MSRC advisory for CVE-2026-70113), and the issue is tracked as CWE-190 integer overflow or wraparound.
Heap-based buffer overflow in the Microsoft Windows Storage Spaces driver (Spaceport.sys) allows an authenticated, low-privileged local user to execute code in kernel context and elevate privileges, carrying a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The attacker must already hold a session on the target host, so this is best treated as a post-compromise privilege-escalation step rather than a remote entry point, and no user interaction is required beyond the existing local session. Vendor-released patches exist for all affected Windows 10, Windows 11 and Windows Server builds; no public exploit code has been identified at time of analysis and CISA's SSVC assessment records exploitation as "none". Compared with network-facing, pre-authentication bugs this rates as a credible but not emergency-tier priority: patch it on a normal cycle, but prioritize systems where untrusted or low-privileged users can obtain local interactive sessions.
Elevation of privilege in the Microsoft Windows Kernel lets an unauthenticated, remote attacker who can reach the affected kernel code path corrupt or redirect kernel memory and gain SYSTEM-level control of the target host. All currently supported Windows client and server families are in scope - Windows 10 (1607, 1809, 21H2, 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025, including Server Core installations - and the assessment vector (AV:N/AC:H/PR:N/UI:N, C:H/I:H/A:H, base 8.1) confirms no credentials or user interaction are needed. The decisive limitation is attack complexity: the attacker must control or influence an untrusted pointer and win a precise kernel memory-layout or timing condition, so this is not a single-shot request. Microsoft has published a fix and there is confirmed vendor patch availability, but no CISA KEV listing and no public exploit code identified at time of analysis; the practical verdict is a genuine high-priority patching candidate rather than a drop-everything emergency.
Local privilege escalation in the Microsoft PostScript Printer Driver allows a low-privileged user on an affected Windows host to gain elevated code execution by having attacker-controlled PostScript/print-driver data processed on the machine, with the root cause classified as a CWE-121 stack-based buffer overflow and a CVSS base score of 7.8. The vector (AV:L/AC:L/PR:N/UI:R) shows no privileges are required prior to exploitation (PR:N) but local presence is mandatory and the victim must be induced to trigger processing of the malicious data (UI:R); CISA's SSVC assessment records Exploitation=none and Automatable=no, and no public exploit code has been identified at time of analysis. This is a credible but context-dependent post-compromise escalation step rather than a mass-exploitation emergency, and a vendor patch is available.
A heap-based buffer overflow (CWE-122) in the Microsoft PostScript Printer Driver lets a local attacker who persuades a victim to process a crafted PostScript print job or document elevate privileges on affected Windows client and server releases. The flaw requires local access (AV:L) and user interaction (UI:R) but no prior privileges (PR:N), so it is a targeted rather than opportunistic local privilege-escalation vector; CISA SSVC rates it non-automatable with no observed exploitation, and no public exploit code has been identified at time of analysis. Vendor patches are available and, per the assessed impact (C:H/I:H/A:H), successful exploitation gives full code execution in the driver's higher-privileged context.
Heap-based buffer overflow in the Windows Win32 kernel subsystem lets a locally authenticated low-privilege attacker escalate to full system privileges on an affected host. Every supported Windows build in the EUVD-listed ranges is exposed by default - Windows 10 21H2 and 22H2, Windows 11 23H2 through 26H2 (including 26H1), and Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025 in both full and Server Core installations - until the corresponding cumulative update is applied; CVSS 3.1 is 7.8 (AV:L/PR:L/UI:N/S:U/C:H/I:H/A:H), so impact on confidentiality, integrity and availability is total once the primitive is triggered. Microsoft has published fixes in its update guide, and no public exploit code or active exploitation has been identified at time of analysis (CISA SSVC exploitation: none). The practical barrier is that the attacker must already hold local code execution on the target, making this a post-compromise privilege-escalation step rather than an initial-access vector.
Heap-based buffer overflow in the Windows kernel (CVE-2026-70106) allows an attacker who already holds low-privileged local code execution to elevate privileges on the affected host, scoring 7.8 under CVSS v3.1 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Exposure is broad across build numbers - Windows 10, Windows 11 and Windows Server 2012 through 2025, including Server Core - but the attack is gated behind an existing local foothold, so it is a post-compromise escalation primitive rather than a remotely reachable one. Microsoft has released fixes through the MSRC update guide, and no public exploit code or confirmed active exploitation was identified at time of analysis (CISA SSVC exploitation: none).
Local privilege escalation in the Windows Win32 Kernel Subsystem lets an attacker who already holds low-privileged, authenticated code execution on a Windows host raise their privileges to kernel level. The flaw is an untrusted pointer dereference (CWE-822) in the kernel that can be triggered with low attack complexity and no user interaction, giving high impact to confidentiality, integrity, and availability (CVSS 3.1 7.8, AV:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No public exploit code has been identified and CISA's SSVC assessment records exploitation as none and automatable as no, so this is a credible but not emergency-level priority; the main constraint on attackers is the need for a pre-existing local foothold on an unpatched build.
Heap-based buffer overflow in Microsoft Windows Error Reporting (WER) lets a locally authenticated attacker holding only low-level privileges elevate their privileges on the host, with full confidentiality, integrity and availability impact (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). No user interaction or non-default configuration is required because WER is a built-in subsystem present across every affected Windows 10, Windows 11 and Windows Server 2016-2025 SKU, but the flaw is not remotely exploitable: the attacker must already be able to run code locally under a valid low-privilege account. There is no confirmed active exploitation (the CVE is not in CISA KEV) and no public exploit code identified at time of analysis; Microsoft has published a fix and an advisory entry for the issue, so affected builds below the fixed thresholds should be updated.
Local privilege escalation in the Microsoft Windows Storage Spaces driver (Spaceport.sys) lets an authenticated, low-privileged attacker who already has code execution on a host corrupt kernel memory and obtain SYSTEM-level rights. The defect is a use-after-free (CWE-416) that is locally reachable with low attack complexity and no user interaction, and it affects Windows 10, Windows 11 and Windows Server builds below the fixed versions enumerated in the vendor update. No public exploit code has been identified and CISA's SSVC decision data records no exploitation activity, so this is a genuine but second-tier patching priority relative to any actively exploited issue in the same release cycle.
Heap-based buffer overflow in the Windows iSCSI Initiator component allows a remote unauthenticated attacker to execute arbitrary code on affected Windows 10, Windows 11, and Windows Server 2012 through 2025 systems, provided the target actually uses iSCSI and a user or administrator initiates or accepts a connection to an attacker-controlled iSCSI target (CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, base 7.5). The user-interaction requirement and High attack complexity - the attacker must also satisfy memory-layout or timing conditions to convert the overflow into reliable code execution - sharply limit the practical attack surface to environments that deploy iSCSI storage. Vendor-released patches are available from Microsoft, CISA's SSVC decision framework rates exploitation as none and automatable as no, and no public exploit identified at time of analysis.
Local privilege escalation in the Windows Rich Text Edit Control (the riched20/msftedit engine used by WordPad, Outlook, and many applications that render Rich Text Format content) lets an attacker who already holds authenticated low-privileged access on a Windows host trigger a heap-based buffer overflow and obtain higher-integrity code execution. Exploitation requires the attacker to invoke the control with attacker-controlled rich-text content (CVSS PR:L, UI:N), so it is a post-compromise escalation primitive rather than a remote or unauthenticated path; SSVC rates the technical impact as total but flags the issue as not automatable, meaning reliable mass exploitation is unlikely, and no public exploit was identified at time of analysis. Microsoft has published a vendor fix, so the residual risk is concentrated on unpatched Windows 10, Windows 11, and Windows Server builds where a low-privileged foothold already exists.
Local privilege escalation in the Microsoft PostScript Printer Driver allows an attacker who gets a victim to open or print a crafted PostScript payload to trigger a heap-based buffer overflow (CWE-122) and execute code in the context of the affected Windows printing component. The flaw affects a broad range of Windows client and server builds - including Windows 10/11 and Windows Server 2012 through 2025 - that have not been updated to their fixed build revision. Per the CVSS vector the attacker needs no pre-existing account (PR:N), but exploitation is local (AV:L) and requires user interaction (UI:R), a crafted document must be processed on the target, and no public exploit code or active exploitation was identified at time of analysis (CISA SSVC: Exploitation = none, Automatable = no).
Heap-based buffer overflow in Microsoft Windows GDI (CWE-122) lets remote attackers achieve code execution on a fully updated-adjacent target by convincing a user to open or preview a maliciously crafted image or document that is parsed through the Windows Graphics Device Interface; the CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (8.8) indicates no authentication is needed but that the victim must interact with the attacker-supplied file. Code execution occurs in the security context of the user who opened the file, so the impact is bounded by that user's privileges and no scope change occurs. No public exploit code has been identified at time of analysis and the CISA SSVC decision framework records Exploitation: none with Automatable: no, while Technical Impact is rated total; there is no KEV listing, so this is a high-priority patching item rather than an emergency. Microsoft has published fixed builds covering Windows 10, Windows 11 and Windows Server 2012 through 2025.
Local privilege escalation in Microsoft's Windows Search Component lets an authenticated attacker who already holds a low-privileged session on a Windows host trigger a use-after-free and elevate to a more privileged security context on the same machine. Exploitation is constrained by a high attack complexity rating (AC:H), reflecting a race/timing condition on the freed object that must be won reliably, and the vector (AV:L/PR:L/UI:N) confirms the attacker must already be logged in locally with low privileges; there is no remote attack surface and no victim interaction required. Patches are available from Microsoft (fixed builds such as Windows 11 24H2 10.0.26100.9711 or later), CISA's SSVC assessment records exploitation as none and the issue as not automatable, and no public exploit code has been identified at time of analysis.
Local privilege escalation in the Windows Win32 Kernel Subsystem lets an attacker who already holds low-privileged, authenticated local access on a vulnerable Windows host corrupt kernel memory and elevate to higher privilege, including SYSTEM-level execution. Only specific builds are exposed: Windows 11 24H2, 25H2, 26H1 and 26H2, plus Windows Server 2025 (including Server Core), at build levels below the vendor's fixed releases. Exploitation is constrained by high attack complexity - the use-after-free must be won as a race/timing condition to reclaim the freed Win32 kernel object before it is reused, which limits reliability and makes the flaw non-automatable per CISA SSVC; no public exploit code has been identified at time of analysis and there is no confirmed active exploitation (KEV), though the high confidentiality, integrity and availability impact and full technical impact score make timely patching important.
Privilege elevation on unpatched Windows hosts is possible through a heap-based buffer overflow (CWE-122) in the Client-Side Caching (CSC) / Offline Files service, which caches content fetched from SMB network shares. The assessed vector (AV:N/AC:L/PR:N/UI:R) describes an unauthenticated remote attacker, but success hinges on a victim interacting - typically by connecting to or accessing an attacker-controlled share so CSC parses a crafted response and overflows a heap buffer - which is consistent with SSVC rating automatic exploitation as 'no' and with the SSVC exploitation signal of 'none'. Microsoft has released patches for every affected build, and no public exploit code has been identified at time of analysis, so this is a serious but not emergency-grade issue demanding prompt, scheduled patching rather than crisis response.
Local privilege escalation to SYSTEM in the Windows Win32k kernel subsystem affects Windows 10, Windows 11, and Windows Server releases, allowing an authenticated low-privileged attacker already executing code on the host to exploit a use-after-free (CWE-416) condition and gain full kernel-level control (CVSS 3.1 7.0, AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H). The high attack complexity (AC:H) reflects the need to reliably win a race or groom the kernel heap, and there is no remote or network vector, so multi-user, RDP/terminal-server, and kiosk systems are the most relevant risk surface. No public exploit code or active exploitation has been identified at time of analysis.
Integer underflow in the Windows Kerberos authentication component allows a locally authenticated attacker to elevate privileges on an affected host, giving full control over confidentiality, integrity, and availability of the machine. Exploitation requires a prior foothold: the attacker must already hold a valid low-privileged local account (PR:L, AV:L), and no user interaction is needed once that access exists; the flaw is not remotely reachable and SSVC rates it non-automatable, so it cannot be driven at mass or wormable scale. No public exploit code has been identified at time of analysis and there is no confirmed active exploitation (CISA KEV), but a vendor patch is available from Microsoft and should be applied to the extensive list of affected Windows 10, Windows 11, and Windows Server builds.
Memory corruption in the libarchive component bundled with Windows (the library behind tar.exe/bsdtar) lets a remote, unauthenticated attacker execute code on affected hosts by having them process a maliciously crafted archive. The root cause is a double free (CWE-415) during archive parsing that corrupts the heap, and because reliably converting that corruption into code execution requires precise heap grooming, Microsoft and our own assessment both rate attack complexity as High despite a CVSS base score of 8.1. No public exploit code has been identified at time of analysis, CISA's SSVC decision framework records exploitation as none and automatable as no, and vendor patches are already available for every affected Windows 10, Windows 11 and Windows Server branch, so this is a serious-but-not-emergency issue that should be closed on a normal patch cadence. One caveat: Microsoft's vector lists UI:N (no user interaction) while our independent assessment uses UI:R, since in interactive deployments a user or application typically has to initiate extraction of the hostile archive - an unattended/service context is where the impact is highest.
Local privilege escalation in the Microsoft Windows Win32 kernel subsystem allows an attacker who already holds low-privilege local access on a Windows host to corrupt heap memory and gain SYSTEM-level code execution. The flaw is a heap-based buffer overflow (CWE-122) rated CVSS 7.8 with a vector of AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning the attacker must be authenticated locally (PR:L, AV:L) and needs to run a crafted program that reaches the vulnerable kernel code path, with no user interaction required. There is no public exploit identified at time of analysis, CISA's SSVC assessment records Exploitation=none and Automatable=no, and vendor-released patches are available for all affected Windows client and server builds.
Local privilege escalation in Microsoft Windows OLE allows an authenticated attacker who already holds a low-privileged foothold on a host to corrupt heap memory through crafted OLE object handling and execute code at a higher integrity level, matching the assessed CVSS:3.1 vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (7.8). Scope is limited to unpatched Windows 10, Windows 11 and Windows Server 2012 through 2025 builds listed by EUVD; because the vector is local-only with PR:L, the flaw is not remotely reachable and cannot be triggered against a default configuration by an outside party. CISA SSVC rates exploitation as "none" and automatable as "no", there is no public exploit identified at time of analysis, and Microsoft has shipped fixes via its Update Guide, making this a credible but not emergency-level priority.
Local privilege escalation in the Windows Update Service allows an attacker who already possesses valid low-privileged local access on an affected Windows host to elevate to a higher-integrity context (including SYSTEM) by triggering a use-after-free. The attack is entirely local - there is no network-facing path - and the assessed vector (AV:L/AC:H/PR:L/UI:N) means successful exploitation depends on winning a race/timing window inherent to the memory-reuse condition, so reliable elevation may require multiple attempts and is not a deterministic one-shot. Affected unpatched builds span Windows 10 21H2/22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2019/2022/2025 (Server Core included); no public exploit code has been identified at time of analysis and there is no CISA KEV confirmation of active exploitation, making this a legitimate but moderate-priority LPE rather than an urgent, broadly exploited threat.
Heap-based memory corruption in the Windows NetBIOS component lets an authenticated local attacker with only low-privileged code execution elevate to SYSTEM on unpatched hosts. Exploitation requires an existing foothold - a valid local account and the ability to run code on the target - so this is a post-compromise escalation primitive, not a remote or initial-access vector; no user interaction is required (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, 7.8). Microsoft has released fixes and CISA's SSVC assessment rates exploitation as 'none' and the issue as non-automatable, so despite a total technical impact this rates as a genuine but not emergency-tier priority; no public exploit code was identified at time of analysis.
Authenticated local code execution in Windows PowerShell affects Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2) and Windows Server 2022/2025, where a heap buffer overflow triggered by crafted input lets a low-privilege local user run code at the level of the PowerShell process. CVSS 3.1 rates it 7.8 (AV:L/AC:L/PR:L/UI:N, high confidentiality, integrity and availability impact), and because the vector requires an existing local interactive session, the practical exposure is privilege escalation or post-foothold activity on shared hosts rather than a remote or unauthenticated attack. No public exploit code has been identified at time of analysis, CISA's SSVC assessment records exploitation as 'none' and automatable as 'no', and Microsoft has released fixed builds through the MSRC update guide.
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.
A heap-based buffer overflow in the Windows Resilient File System (ReFS) driver (refs.sys) allows a locally authenticated, low-privileged attacker to corrupt kernel heap memory and elevate privileges to SYSTEM on affected Windows 10, Windows 11, and Windows Server builds. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) and requires the attacker to already have a foothold on the host plus the ability to feed attacker-controlled input through the ReFS code path, which in practice means a ReFS-formatted volume must be present or mounted for the driver to process that input. Vendor patches are available per the Microsoft advisory, and no public exploit code has been identified at time of analysis (SSVC: Exploitation none, Automatable no); CISA's SSVC framing rates technical impact as total if successfully triggered, but the local-only, authenticated prerequisite and the non-default status of ReFS keep real-world urgency moderate.
Local privilege escalation in Windows Work Folders allows an attacker who already holds authenticated, low-privileged access on an affected Windows 10, Windows 11, or Windows Server host to trigger a use-after-free in the Work Folders code path, corrupting memory and potentially executing code with elevated privileges. The independently assessed vector (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0) confirms this is a post-compromise escalation step that requires an existing local foothold and a reliably won race/timing window, with no user interaction; there is no public exploit identified at time of analysis and CISA's SSVC assessment records exploitation as none and automatable as no. Microsoft has released fixed builds through the MSRC update guide, so the primary risk is to unpatched hosts where the Work Folders feature is present and in use.
Remote code execution in the Microsoft Windows iSCSI Initiator component (reported against Windows releases carrying the affected MSiSCSI/iSCSI code path) allows an unauthenticated, remote attacker to corrupt heap memory and execute arbitrary code in the context of the iSCSI service by driving a crafted iSCSI protocol exchange against the target. The flaw is a memory-safety defect (reported as a use-after-free, with vendor metadata also flagging buffer/heap overflow and denial-of-service characteristics) reachable from CVSS vector AV:N/AC:H/PR:N/UI:N, so no credentials or user interaction are needed and impact is scored C:H/I:H/A:H - full confidentiality, integrity and availability loss on the host. Exploitation is gated by prerequisites rather than by authentication: the victim host must have the iSCSI Initiator running and must establish a session with an attacker-controlled or spoofed iSCSI target, and the AC:H rating reflects a race/timing condition (or protocol state dependency) the attacker must win reliably. No public exploit code and no confirmed active exploitation (no CISA KEV listing) were identified at time of analysis, so this should be prioritized on exposure and asset criticality rather than on observed in-the-wild activity.
Heap corruption in the Microsoft Windows iSCSI service lets an unauthenticated remote attacker crash or destabilize the service, yielding a denial-of-service condition on any host that has the iSCSI listener enabled and network-reachable. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) confirms network reachability with no credentials, no user interaction, and no non-default configuration beyond the service being turned on, and the impact is confined to availability with no data disclosure or modification. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no EPSS or CISA KEV signal was supplied; exposure is therefore driven primarily by deployment, since hosts that do not run the iSCSI service or that firewall its port are not reachable.
Local privilege escalation in Microsoft's Windows Subsystem for Linux (WSL) allows an authenticated low-privileged user with an existing local foothold to corrupt heap memory in the host-side WSL components and cross a security boundary to gain elevated code execution, rated CVSS 7.8 (CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, CWE-122). The attack is entirely local - there is no network vector - and it requires the optional WSL feature to already be installed and enabled on an affected Windows 10, Windows 11 or Windows Server build, which meaningfully limits the exposed population since WSL is not present by default. Microsoft has published a fix through the MSRC update guide and there is no public exploit identified at time of analysis; CISA's SSVC assessment records exploitation as none and automatable as no.
Use-after-free in Windows Secure Kernel Mode allows an authenticated attacker running code locally on the target with low/standard-user privileges to escalate to higher privilege levels on affected Windows 10, Windows 11 and Windows Server 2019-2025 builds that are below their patched versions. The flaw is rated CVSS 7.0 (HIGH); no public exploit code or confirmed active exploitation (CISA KEV) has been identified at time of analysis, and exploitation is gated by high attack complexity because a reliable UAF typically requires winning a timing race or precisely grooming Secure Kernel memory. Microsoft has released vendor patches - applying the fixed builds removes the condition entirely.
Remote unauthenticated code execution affects Microsoft Internet Information Services (IIS) on Windows: a stack-based buffer overflow in a request-handling parsing path is reachable over the network by anyone who can send crafted input to a running IIS instance. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) indicates no authentication, no user interaction, and no prior privileges are needed, and a successful exploit yields full loss of confidentiality, integrity, and availability on the host. No public exploit code was identified at time of analysis and there is no CISA KEV listing, but the combination of low attack complexity and unauthenticated network reachability makes this a high-priority item for any internet-facing IIS deployment; version and build specifics must be confirmed from Microsoft's advisory, since no CPE or version detail is provided in the available intelligence.
Local privilege escalation in Microsoft Windows Hyper-V lets an authenticated, low-privileged attacker who already has code execution on a host with the Hyper-V role enabled trigger a use-after-free in a Hyper-V component and gain SYSTEM-level code execution (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U with C:H/I:H/A:H). Affected builds span Windows 10 1809/21H2/22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2019, 2022, and 2025 including Server Core installations; no public exploit code has been identified at time of analysis and CISA SSVC records exploitation as none with Automatable: no, so risk is concentrated on multi-tenant, shared, or virtualization hosts where untrusted low-privilege principals already run. Microsoft has released fixes through the standard Windows cumulative update channel (MSRC advisory CVE-2026-70023, mirrored in ENISA EUVD-2026-100338), and administrators of Hyper-V hosts should treat this as a priority local escalation patch rather than a remote emergency.
Local privilege escalation in Windows Direct Composition (DComp) lets an attacker who already has low-privileged code execution on an affected Windows 11 or Windows Server host escalate to SYSTEM-level privileges. The flaw is a use-after-free (CWE-416) that requires winning a heap-grooming race window, so it is rated high complexity (AC:H) and carries a CVSS of 7.0; exploitation is local and the attacker must be authenticated (PR:L, AV:L) with no user interaction needed (UI:N). Microsoft has released fixes for every affected branch, and there is no public exploit identified at time of analysis - CISA's SSVC assessment records exploitation as "none," making this a moderate-priority patch item rather than an emergency.
Local privilege escalation in the Windows Local Security Authority Subsystem Service (LSASS) allows an authenticated attacker with an existing low-privileged foothold on a host to corrupt heap memory inside the LSASS process and elevate privileges to the level LSASS runs at (SYSTEM). The flaw carries a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation is local, low-complexity, requires no user interaction, and is confined to the same security scope, so it is a post-compromise escalation step rather than an initial access vector. At time of analysis there is no public exploit identified, CISA's SSVC assessment records Exploitation: none, and the issue is not listed in KEV; a vendor patch is available, so the practical priority is routine patch-cycle remediation rather than emergency response.
Code execution in Windows Cryptographic Services is possible when an authenticated attacker with valid low-privilege credentials and network reachability to the affected host wins a memory-lifecycle race in a freed object (use-after-free). Successful exploitation yields high confidentiality and integrity impact, but the high attack complexity (AC:H) means it depends on non-deterministic heap timing rather than a deterministic trigger, and the CVSS vector requires PR:L, so unauthenticated remote exploitation is not described. No public exploit has been identified at time of analysis, CISA SSVC records Exploitation=none and Automatable=no, and vendor patches are already available for every listed Windows client and server build.
Remote code execution in the Windows iSCSI initiator stack (CVE-2026-70013) allows a network-adjacent attacker to execute arbitrary code with high confidentiality, integrity and availability impact. Affected are the Windows iSCSI components shipped across Windows 10, Windows 11 (23H2 through 26H2) and Windows Server 2012 through Server 2025, including Server Core installations, with vendor fixes now published. Exploitation requires an active iSCSI session - typically a target the attacker controls or can inject responses into - and, because the flaw is a use-after-free race (CWE-416, AC:H), success depends on winning a memory-reuse timing window rather than issuing a single deterministic request; no public exploit code has been identified at time of analysis and CISA's SSVC assessment records Exploitation: none, so this is a serious-but-not-emergency priority rather than an active incident.
Use-after-free in the Windows Remote Desktop Client lets an unauthenticated attacker execute arbitrary code on a connecting client by luring a user into initiating an RDP session to an attacker-controlled or compromised server. The vector is network-reachable with no privileges required (PR:N), but practical exploitation depends on the victim starting the outbound connection (UI:R) and on the attacker winning a specific memory-state or timing condition (AC:H), which is consistent with CISA's SSVC rating of non-automatable and no observed exploitation. No public exploit code has been identified at time of analysis and Microsoft has published fixed builds covering all affected Windows 10, Windows 11 and Windows Server platforms; because the trigger is client-initiated rather than a passive listening service, the realistic delivery paths are malicious .rdp files, crafted links, or a hijacked RDP endpoint.
Local privilege escalation in Microsoft Windows NTFS (CVE-2026-70010) allows an authenticated, low-privileged user to corrupt kernel heap memory via crafted NTFS filesystem operations and elevate to SYSTEM. The flaw is a heap-based buffer overflow (CWE-122) in the in-kernel NTFS driver, rated CVSS 7.8 (HIGH) with the vector AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, meaning the attacker must already hold a local foothold on the host but needs no user interaction and faces low attack complexity. Exploitation is not remotely reachable over the network, no public exploit code has been identified at time of analysis, and CISA's SSVC assessment records exploitation as 'none'; patch availability is confirmed through the Microsoft MSRC update guide.
Local privilege escalation in the Windows IP Over USB Service (IpOverUsbSvc) allows an attacker who already holds a low-privileged, authenticated session on a Windows host to overflow an integer value and consequently gain SYSTEM-level code execution, with high impact to confidentiality, integrity, and availability. Affected builds span Windows 10 (21H2/22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), and Windows Server 2022/2025 according to the EUVD version ranges, although the vulnerable service ships with developer/SDK and device-debugging tooling rather than being enabled on default installations. Exploitation requires local access and the service to be installed and running, so the practical fleet at risk is developer and debugging workstations; there is no public exploit identified at time of analysis and the issue is not confirmed actively exploited (CISA KEV), and a vendor patch is available.
A use-after-free (CWE-416) in the Microsoft Windows Remote Desktop Client allows an unauthenticated attacker to execute code on a victim's machine when that user initiates an outbound connection to an attacker-controlled RDP server. The flaw is client-side rather than a remotely reachable service bug: the attacker must control the server endpoint and also win a race condition inherent to the use-after-free (AC:H), while the victim must open a crafted .rdp file or otherwise accept the connection (UI:R), which is why the CVSS 3.1 base score sits at 7.5 even though a successful exploit yields full confidentiality, integrity and availability impact. Vendor-released patches are available, no public exploit code has been identified at time of analysis, and CISA's SSVC assessment records exploitation as none and automatable as no, so this is a moderate-priority issue rather than an urgent one.
Use-after-free in the Windows Remote Desktop Client allows a malicious or compromised RDP server to execute code on a Windows machine that connects to it, affecting builds across Windows 10, Windows 11 (23H2 through 26H2), and Windows Server 2012 through 2025. Exploitation is client-side: an attacker must induce a victim to open a crafted .rdp file or otherwise initiate an outbound RDP session, and with AC:H plus mandatory UI:R, reliable code execution depends on winning a heap race rather than a single deterministic response, so mass opportunistic exploitation is unlikely while targeted social-engineering delivery is plausible. No public exploit identified at time of analysis; CISA's SSVC rates exploitation as none and automation as not automatable, and the PR:N vector means the victim need not authenticate to the attacker.
A use-after-free (CWE-416) in the Windows Remote Desktop Client lets an attacker who controls or compromises an RDP server execute arbitrary code on the connecting client, as described in Microsoft's MSRC advisory for CVE-2026-69998. Exploitation is not passive: the victim must actively initiate an RDP session to the hostile endpoint (UI:R), and the unauthenticated attacker (PR:N) must still win a memory-management race or reliably groom the freed heap object to convert the corruption into code execution (AC:H), giving a CVSS 3.1 base score of 7.5. All supported Windows client and server builds below the patched build levels are affected; there is no public exploit identified at time of analysis, no confirmed active exploitation (CISA KEV), and CISA SSVC records exploitation as none and automatable as no, so the practical risk is driven by social engineering of an outbound RDP connection plus patch lag.
Use-after-free memory corruption in the Microsoft Windows Remote Desktop Client (mstsc.exe) can let an unauthenticated remote attacker execute arbitrary code on a vulnerable client, but only after the victim initiates an outbound RDP connection to an attacker-controlled, compromised, or spoofed RDP server. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, 7.5) confirms the mandatory user interaction and high attack complexity, and CISA's SSVC assessment records exploitation as 'none' and automatable as 'no'; no public exploit code has been identified at time of analysis. Microsoft has released fixes via the MSRC update guide, so the practical risk is moderate and concentrated on hosts that routinely open RDP sessions to untrusted or third-party endpoints.
Use-after-free in the Windows Remote Desktop Client allows a malicious or compromised RDP server to corrupt memory and execute code on the machine that connects to it (CVSS 7.5, C:H/I:H/A:H, SSVC Technical Impact 'total'). The attack is client-initiated and outbound - it requires the victim to establish an RDP session to the hostile endpoint (UI:R) and a favorable memory/race condition to be won (AC:H) - so it does not target a listening RDP service, and no privileges are required on the client (PR:N, unauthenticated). Current intelligence indicates no public exploit code and no confirmed active exploitation (CISA SSVC Exploitation: none; Automatable: no), while Microsoft has released a vendor patch, making this a high-impact-but-not-urgent issue at time of analysis.
Code execution in the Windows Remote Desktop Client (mstsc) is possible when a user initiates an outbound RDP session to a malicious or attacker-controlled server, triggering a use-after-free that can be leveraged for arbitrary code in the client's context. Affected are unpatched Windows client and server builds below their fixed versions - including Windows 10 1607 through 22H2, Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2012/2012 R2/2016/2019/2022/2025 - while the attacker requires no credentials (PR:N) and the flaw cannot be triggered against a listening host without the victim's outbound connection (UI:R). Exploitation is rated high-complexity (AC:H) because the attacker must reliably win the heap/timing-dependent memory corruption condition; there is no public exploit identified at time of analysis and no confirmed active exploitation (CISA KEV), and Microsoft has released patched builds.
Use-after-free memory corruption in the Windows Remote Desktop Client allows an unauthenticated remote attacker to execute code in the context of the connecting user, but only after the victim initiates an outbound RDP session to an attacker-controlled or compromised server. Microsoft rates the issue 7.5 (High) under CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H, reflecting a total loss of confidentiality, integrity, and availability that is tempered by high attack complexity and mandatory user interaction. CISA's SSVC assessment records exploitation as 'none' and no public exploit identified at time of analysis; Microsoft has released fixed builds through its update guide.
Remote code execution in Windows Remote Desktop Services is possible through a use-after-free (CWE-416) in the RDP component, rated CVSS 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H). An unauthenticated remote attacker can achieve high confidentiality, integrity, and availability impact, but exploitation is not reliable: the attacker must satisfy a race or heap-grooming condition (AC:H), and a victim must initiate or accept a Remote Desktop connection to an attacker-controlled endpoint (UI:R). No public exploit code is identified at time of analysis, CISA SSVC records exploitation as none, and Microsoft has released patches; hosts without the Remote Desktop/RDS role enabled are not exposed, so risk is concentrated on internet- or untrusted-network-facing RDP deployments.
Remote code execution in Microsoft's Windows Remote Desktop Client stems from a use-after-free (CWE-416) triggered when the client processes crafted data supplied by an RDP server. An unauthenticated attacker can exploit this over a network only by inducing a user to connect to an attacker-controlled or compromised RDP server - for example by opening a malicious .rdp file or link - after which heap corruption can lead to code execution in the context of the client. The CVSS 3.1 base score is 7.5 (AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H), reflecting required user interaction and high attack complexity; CISA's SSVC assessment rates exploitation as 'none' and automatable as 'no', no public exploit code has been identified at time of analysis, and the vulnerability has not been confirmed actively exploited (CISA KEV). Vendor patches are available, so the practical risk is concentrated in unpatched Windows clients exposed to untrusted RDP endpoints.
Remote code execution affects the Windows Remote Desktop Client (mstsc) across a wide range of supported desktop and server builds, allowing an attacker who controls or manipulates an RDP endpoint to execute code in the context of the connecting user. The flaw is a use-after-free (CWE-416) rated CVSS 7.5; exploitation requires the victim to actively initiate an RDP session outward to the hostile server (UI:R), and high attack complexity (AC:H) reflects dependence on heap/race conditions rather than a deterministic trigger - no authentication is required of the attacker (PR:N). No public exploit code has been identified at time of analysis and CISA's SSVC records Exploitation=none with no KEV listing, so risk is driven by the breadth of affected Windows builds and the total technical impact should the memory-corruption primitive be reliably converted into code execution.
Outbound RDP sessions from the Windows Remote Desktop Client can be turned against the client itself: when a user connects to an attacker-controlled, compromised, or man-in-the-middle'd RDP server, crafted response data triggers a use-after-free (CWE-416) that can lead to code execution on the victim's machine, with total technical impact if the memory corruption is reliably steered. The attacker needs no credentials on the client (PR:N) and can operate remotely over the network (AV:N), but exploitation is gated by mandatory user interaction (the user must actively initiate the session, UI:R) and high attack complexity (AC:H) reflecting the precision required to trigger and control the freed allocation. Microsoft rates this CVSS 7.5 and has released vendor patches; there is no public exploit identified at time of analysis and no evidence of exploitation - CISA's SSVC assessment records Exploitation: none and Automatable: no.
A use-after-free (CWE-416) in the Windows Remote Desktop Client (mstsc.exe / RDP client stack) allows remote code execution in the security context of the connecting user when that user establishes an outbound RDP session to an attacker-controlled or compromised RDP server. Exploitation is unauthenticated with respect to the client (CVSS 3.1 PR:N) but requires user interaction (UI:R) and is rated high attack complexity (AC:H), because the attacker must deliver crafted server-side RDP protocol data and win a race condition over the freed object; the resulting impact is full compromise of confidentiality, integrity and availability within the user's own security scope (S:U, no privilege escalation to SYSTEM). Microsoft has released a vendor patch covering Windows 10, Windows 11 and Windows Server 2012 through 2025, exploitation has not been observed by CISA SSVC assessment (Exploitation: none, Automatable: no), and no public exploit code was identified at the time of analysis.
Heap-based buffer overflow in the Windows Libarchive component - the library Windows uses to extract 7z, rar, tar, cab and similar archive formats - lets a remote attacker execute arbitrary code with the privileges of the user who opens a malicious archive. Because exploitation is delivered over the network (AV:N) with no authentication required (PR:N) but demands that the victim open or process the crafted file (UI:R), the realistic attack path is a phishing email attachment, a web download, or a hosted share rather than anything wormable; CISA's SSVC decision framework reflects this with Exploitation=none and Automatable=no. There is no public exploit identified at time of analysis and vendor patches are available, so the practical priority is patch deployment rather than emergency containment - while noting the CVSS 8.8 score masks that the mandatory user interaction is the single factor keeping risk below critical.
Use-after-free (CWE-416) in the Windows Remote Desktop Client (mstsc) allows remote code execution on a Windows client that connects out to a malicious or compromised RDP server, affecting all supported Windows 10, Windows 11, and Windows Server builds below the fixed patch levels listed in Microsoft's advisory. Exploitation is not opportunistic: it follows a reverse-RDP pattern in which the victim must initiate the session (UI:R) against attacker-controlled server infrastructure, and public exploitation is not confirmed - CISA SSVC records exploitation as 'none' and no public exploit code has been identified at time of analysis. The negotiated CVSS of 7.5 is driven by high attack complexity (AC:H), reflecting the heap-state and timing control needed to win the use-after-free race, while requiring no privileges on the victim (PR:N) and impacting confidentiality, integrity, and availability equally.
Local privilege escalation in Microsoft's Quality Windows Audio/Video Experience (QWAVE) service stems from a use-after-free condition (CWE-416) that can let an already-authenticated local user execute code in the service's more privileged context, with high impact to confidentiality, integrity and availability (C:H/I:H/A:H). Rated CVSS 7.0 with a vector of AV:L/AC:H/PR:L/UI:N/S:U, exploitation requires an attacker who already holds a local account on the host and who can also win a timing or object-lifetime race - CISA's SSVC assessment records Exploitation=none and Automatable=no, and there is no public exploit identified at time of analysis. Microsoft has shipped vendor-released patches for every affected branch, so this is best treated as a moderate-priority post-foothold escalation whose realistic risk is lower than the base score alone suggests, rather than an emergency to be handled outside the normal patch cycle.
Remote code execution in the Microsoft Remote Desktop Client (CWE-416) occurs when a user initiates an RDP connection to an attacker-controlled or compromised server that returns crafted responses, causing the client to reuse a freed memory object. The CVSS vector (AV:N/AC:H/PR:N/UI:R) shows an unauthenticated attacker is required to hold no credentials on the victim host, but must convince the user to start the session and satisfy high-complexity heap-timing conditions for reliable exploitation; impact is confined to the connecting user's security context with no privilege escalation implied. Exploitation only triggers on a client that actively connects outbound, and no public exploit identified at time of analysis.
Heap-based buffer overflow in the Microsoft Streaming Service, a Windows kernel-mode component, allows an attacker who already holds local access and low-privileged code execution on the host to elevate to SYSTEM-level privileges. The flaw is not remotely reachable: exploitation requires direct interaction with the affected kernel driver (AV:L) and a high-complexity trigger condition (AC:H), typically a race or a carefully shaped heap layout, so reliable exploitation is non-trivial even though no victim interaction is needed (UI:N). Per the available intelligence, there is no public exploit code and no KEV confirmation, so exploitation status at time of analysis is: no public exploit identified; the primary defence is prompt application of Microsoft's update from the MSRC advisory.
Local privilege escalation in Microsoft Streaming Service on Windows 10, Windows 11 (21H2 through 26H2) and Windows Server 2012 through 2025 allows an authenticated, low-privilege attacker who already has code execution on the host to exploit an integer wraparound and elevate privileges, with total impact to confidentiality, integrity and availability (CVSS 7.8). The flaw is strictly local - the vector (AV:L/PR:L/UI:N) rules out remote or unauthenticated reach - and SSVC records exploitation as none with automatable set to no, so no public exploit code has been identified at time of analysis. This is a genuine patch-priority issue but not an emergency, and it matters most on multi-user, terminal-server and jump hosts where untrusted users can already run code.
Local code execution and information disclosure on patched-but-not-updated Windows hosts can result from an out-of-bounds read in the Windows Overlay Filter (WOF), a kernel-mode filesystem filter driver that services compressed and overlay file operations. Affected are Windows 10 (1607 through 22H2), Windows 11 (23H2, 24H2, 25H2, 26H1, 26H2), and Windows Server 2012 through 2025 in both full and Server Core installations below the builds listed in the vendor update matrix. Exploitation requires a pre-existing local, authenticated foothold with at least low-level privileges (CVSS:3.1/AV:L/AC:L/PR:L/UI:N) - remote, unauthenticated attack is not possible - and no public exploit code has been identified at time of analysis, with SSVC recording Exploitation=none and Automatable=no, placing this in the post-compromise privilege-escalation and information-leak class rather than a wormable emergency. A vendor patch is available and should be applied through the standard Microsoft monthly servicing channel.
Elevation of privilege in the Windows Overlay Filter (WOF) driver allows an attacker who already holds a low-privileged local foothold on a supported Windows host to run code at SYSTEM level by triggering an integer overflow/wraparound during a filter operation. Exploitation is local-only and requires authenticated code execution at low privilege (CVSS:3.1/AV:L/AC:L/PR:L/UI:N, base 7.8) with no user interaction; CISA's SSVC assessment records Exploitation=none and Automatable=no, so there is no public exploit identified at time of analysis. Vendor patches exist for every affected SKU, which materially lowers residual risk for organizations that have applied current servicing updates.
Local privilege escalation in the Microsoft Windows Overlay Filter (WOF) affects default installations of Windows 10, Windows 11, and Windows Server 2012 through 2025 that have not yet applied the fixed builds listed in the EUVD advisory. An attacker who already holds a low-privileged, authenticated local session (CVSS vector PR:L, AV:L) can trigger a buffer over-read in the filter - tracked as CWE-126 - and, on success, gain high confidentiality, integrity, and availability impact as reported by the assessed CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H score of 7.8. No user interaction is required and there is no remote or network attack vector; exploitation status is neutral (SSVC: Exploitation none, Automatable no), with no public exploit identified at time of analysis. This is a genuine but second-tier priority: the vendor has shipped patches, and the flaw is only reachable from an already-compromised local user context.
Out-of-bounds read in the Windows Overlay Filter (wof.sys), a kernel-mode Windows component enabled by default, allows an authenticated local attacker with an existing low-privileged foothold to elevate privileges on the host (CVSS 3.1 base 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Because wof.sys loads by default across supported client and server editions, no non-default configuration is required to reach the vulnerable code; the primary gating factor is the prerequisite of local code execution, and no public exploit has been identified at time of analysis, with CISA SSVC rating exploitation as none and the attack as not automatable. Successful exploitation yields total technical impact per SSVC (high confidentiality, integrity and availability impact), consistent with a kernel-level memory-safety primitive being turned into local privilege escalation.
Local privilege escalation in the Windows Overlay Filter (WOF) driver lets an attacker who already holds low-privileged, authenticated local access on an affected Windows host trigger a buffer over-read (CWE-126) that can be leveraged to gain elevated privileges, with high confidentiality, integrity and availability impact, matching the CVSS 3.1 score of 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). The flaw is not remotely reachable and cannot be used for initial compromise because it requires an existing foothold on the machine, and CISA's SSVC assessment records no observed exploitation while no public exploit has been identified at time of analysis. Microsoft has shipped vendor patches covering the affected Windows 10, Windows 11 and Windows Server 2012 through 2025 builds, so this is best treated as a credible patch-cycle priority rather than an emergency.
Local privilege escalation in the Windows Client for NFS affects systems where the optional Client for NFS feature has been installed, allowing an attacker who already holds authenticated low-privileged local access to trigger a heap-based buffer overflow (CWE-122) and gain full control of the host at the kernel/SYSTEM level. The flaw is rated CVSS 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H), meaning exploitation is local, requires low privileges, needs no user interaction, and is confined to the affected machine - a technically complete compromise but not a remotely reachable or self-propagating one. There is no public exploit identified at time of analysis, CISA's SSVC assessment records Exploitation: none and Automatable: no, and the vendor has released patched builds, so this is best treated as a genuine but second-tier local privilege-escalation issue whose real-world exposure is gated by whether the NFS client component is present.
Local privilege escalation in the Windows AppX Deployment Extensions component allows an authenticated, low-privileged attacker who already has code execution or interactive access on a host to elevate to a higher-integrity context, including SYSTEM, because a required authorization check is missing (CWE-862). The flaw carries a CVSS 3.1 base score of 8.8 from the vector AV:L/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - the Scope:Changed rating reflects that a successful exploit crosses a privilege boundary, granting high confidentiality, integrity, and availability impact. Every supported Windows client and server release is exposed, and because the component ships in default Windows installations, no unusual configuration is required once the attacker has a foothold; there is no KEV listing and no public exploit identified at time of analysis, though the low attack complexity and absence of user interaction make it an attractive post-compromise escalation primitive. Microsoft has released fixed builds, so this is a genuine prioritization candidate for patch cycles rather than an unmitigable emergency, but the hard prerequisite of existing local access is the main constraint on real-world risk.
Code execution in the Windows Overlay Filter (WOF) driver lets a locally authenticated attacker trigger an out-of-bounds memory read and, per Microsoft's severity rating, achieve code execution with high confidentiality, integrity and availability impact on unpatched machines. The flaw (CVE-2026-69942, CWE-126, CVSS 7.8 / AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) requires a pre-existing local foothold and low-privileged credentials, so it is a post-compromise privilege-escalation issue rather than an initial access vector, affecting Windows 11 23H2, 24H2, 25H2, 26H1 and 26H2 plus Windows Server 2022 and Windows Server 2025 (including Server Core) below their fixed build levels. CISA's SSVC assessment records Exploitation: none and Automatable: no, and no public exploit identified at time of analysis; Microsoft has released a fix, so exposure is confined to systems that have not yet installed the current cumulative update.
Local privilege escalation in the Windows Storage component allows an authenticated, low-privileged attacker to gain full control of a Windows host (C:H/I:H/A:H) by winning a race condition that triggers a use-after-free in the storage stack. Exploitation requires an existing local foothold (AV:L, PR:L) and is timing-dependent and non-deterministic (AC:H, CWE-362), so it is a post-compromise escalation primitive rather than a remotely reachable or mass-exploitable bug. This is a moderate-priority local elevation-of-privilege flaw, not an emergency: no public exploit code and no evidence of active exploitation were identified at time of analysis (SSVC Exploitation=none, Automatable=no), and Microsoft has released a vendor patch.
Local privilege escalation in the Windows Spaceport.sys Storage Spaces kernel driver allows an authenticated attacker who already has the ability to execute code as a low-privileged user on an affected host to gain full SYSTEM-level privileges. An integer overflow/wraparound in the driver's handling of size or index values lets a crafted request corrupt kernel memory, yielding complete loss of confidentiality, integrity, and availability (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). All unpatched Windows 11 releases from 23H2 through 26H2, Windows Server 2022, and Windows Server 2025 (including Server Core) installations with the driver loaded at defaults are in scope, but exploitation is not automatable per SSVC, and no public exploit identified at time of analysis.
Local privilege escalation in the Windows Storage component lets an attacker who already holds a foothold on a Windows host with low-level privileges (PR:L) escalate to full system rights by winning a race condition (CWE-362) in the storage subsystem's handling of a shared resource. The attack is entirely local (AV:L), requires no user interaction, and is assessed at CVSS:3.1 base 7.0 with HIGH attack complexity because the timing window is narrow and non-deterministic, which is why CISA's SSVC rates it non-automatable with no observed exploitation; no public exploit code was identified at time of analysis. Because successful escalation grants high confidentiality, integrity and availability impact on the host, unpatched Windows 10, Windows 11 and Windows Server builds exposed to multi-user or post-compromise scenarios should be prioritized for the vendor patch.
Local privilege escalation in Microsoft's Desktop Window Manager (dwm.exe) allows a low-privileged attacker who already has code execution on a Windows system to bring about a type-confusion condition and obtain elevated rights, scored CVSS 3.1 7.8 (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H). Because DWM is present and running by default in every interactive Windows desktop session, no special feature or non-default configuration is required to reach the vulnerable code; only a locally executed crafted program is needed. This is a post-compromise escalation primitive rather than a remote entry point, no public exploit identified at time of analysis, and Microsoft's MSRC update-guide entry is the authoritative reference for affected builds and the fix.