Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
HighPublic exploit

Windows Storage Elevation of Privilege Vulnerability

IdentifiersCVE-2026-21508CWE-287· Improper Authentication

CVE-2026-21508 is an elevation of privilege vulnerability in Windows Storage caused by improper authentication. The available supporting content indicates a logical flaw in windows.storage.dll that can be abused by a local authorized attacker by manipulating the current user’s registry entries and hijacking the CLSID parameter passed to CoCreateInstance when invoked by a higher-privileged process. This can result in unintended execution in a higher-privilege security context and privilege escalation on the local system.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation allows a local authenticated/authorized attacker to elevate privileges, with the supporting advisory indicating escalation to SYSTEM. This can enable full compromise of the affected host’s confidentiality, integrity, and availability, including execution of code or actions as SYSTEM, tampering with protected resources, credential or data access, persistence, and follow-on lateral movement.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, reduce local privilege escalation opportunities by restricting interactive logon and code execution for untrusted users, hardening permissions on user-writable registry locations, monitoring for suspicious modification of per-user COM/CLSID-related registry entries, and detecting anomalous high-privilege process launches that instantiate COM objects from user-influenced registry paths. These measures are compensating controls only and do not replace the vendor patch.

Remediation

Patch, then assume compromise.

Apply Microsoft’s official security update for CVE-2026-21508 for all affected Windows versions via Windows Update, WSUS, or packages from the Microsoft Update Catalog. Prioritize patching supported Windows 10 versions and other affected platforms identified by Microsoft, and verify successful installation through update history or enterprise patch management telemetry.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2026-21508_POCMaturityPoCVerified exploit

Repository is a Windows local privilege-escalation proof-of-concept for CVE-2026-21508. It consists of (1) a batch setup script (SETUP.bat) that stages a malicious DLL and configures per-user COM registry keys under HKCU\Software\Classes\CLSID to influence WUDFHost.exe COM activation, and (2) a Visual Studio C++ DLL project (Session0_CMD) that implements the payload. Key behavior: - SETUP.bat copies a bundled JPG (alps.jpg) to a user-provided USB drive letter to satisfy a condition that at least one .jpg exists on the USB. - It creates C:\ProgramData\CrossDevice and copies the built DLL to C:\ProgramData\CrossDevice\CrossDevice.Streaming.Source.dll (the hijack target name). - It adds/creates specific HKCU CLSID keys to force WUDFHost.exe to instantiate a chosen CLSID and to alter activation flow (per comments: avoid verclsid.exe and call CoCreateInstance directly). - It triggers the vulnerable path by launching Windows Media Player (wmplayer.exe). Payload DLL (Session0_CMD/dllmain.cpp): - On DLL_PROCESS_ATTACH, calls RevertToSelf() to stop impersonation. - Checks token elevation via OpenProcessToken/GetTokenInformation(TokenElevation). - If elevated, spawns C:\Windows\System32\cmd.exe using CreateProcessA, demonstrating code execution in a privileged context (often visible as a WUDFHost.exe child, potentially in Session 0). Repo structure: - Root: README.md (usage steps and links), SETUP.bat (stager/trigger), LICENSE. - Session0_CMD/: Visual Studio solution/project files and minimal C++ source (dllmain.cpp plus precompiled header scaffolding). No network C2 or remote endpoints are present; all observables are local file paths and registry keys used to stage and trigger the hijack.

0xc4rDisclosed Feb 10, 2026batchc++local (Windows) privilege escalation via COM/registry manipulation + DLL hijacking triggered by Windows Media Player/WUDFHost.exe)
EXPOSURE SURFACE

Affected products & vendors

Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
Microsoft CorporationWindows Storageapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity7

Community discussion across Reddit, Mastodon, and other social sources.