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

Winlogon Elevation of Privilege Vulnerability

IdentifiersCVE-2026-25187CWE-59· Improper Link Resolution Before…

CVE-2026-25187 is a local elevation-of-privilege vulnerability in Microsoft Windows Winlogon caused by improper link resolution before file access (link following). The flaw occurs when Winlogon follows a link during file access in a way that can be abused by an authorized local attacker, enabling privilege escalation. Microsoft and third-party reporting describe the issue as affecting the Winlogon process and classify it under CWE-59. Public reporting also notes a CVSS score of 7.8 and that the issue was discovered by Google Project Zero.

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 authorized attacker to elevate privileges on the affected Windows system, with reporting indicating this can result in SYSTEM-level privileges. Because the flaw is in Winlogon, compromise can provide highly privileged execution and full control over the local host.

Mitigation

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

If immediate patching is not possible, reduce exposure by limiting local access to trusted users only, restricting the ability of non-administrative users to create or manipulate links in sensitive filesystem locations, and monitoring for suspicious link-following or file-manipulation activity involving Winlogon-related paths. No specific vendor mitigation beyond patching was provided in the supplied content.

Remediation

Patch, then assume compromise.

Apply Microsoft's March 2026 security update for Windows that addresses CVE-2026-25187. Prioritize patching because Microsoft assessed this vulnerability as 'Exploitation More Likely.'
PUBLIC EXPLOITS

Exploits

No public exploits tracked yet. Mallory keeps watching.

VALID 0 / 0 TOTALView more in app

No public exploit code observed for this vulnerability.

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

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 signatures1

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 activity6

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