Skip to main content
Mallory
HighExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2025-26633: MSC EvilTwin

Published Mar 11, 2025 · Updated 14 days ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.0High · v3.1
EPSS30.4%98th percentile
CISA KEVYesAdded Mar 11, 2025
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2025-26633CWE-707 · Improper Neutralization

CVE-2025-26633, known as MSC EvilTwin, is an improper-neutralization vulnerability in Microsoft Management Console (MMC) that allows an unauthorized attacker to bypass a security feature locally. The vulnerability affects Multilingual User Interface (MUI) path handling: ScOnOpenDocument calls scGetMuiPath, which uses GetFileMUIPath to locate localized resources. An attacker can arrange identically named benign and malicious console files so that opening the benign counterpart causes MMC to load the malicious counterpart's XML from a language-specific subdirectory. Observed exploitation combines this substitution with embedded browser content capable of invoking external.ExecuteShellCommand to download and execute additional malware. Water Gamayun, also tracked as EncryptHub and Larva-208, exploited the vulnerability before Microsoft released a patch on March 11, 2025.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

Impact, mitigation & remediation

What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.

Impact

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

Successful exploitation bypasses MMC security controls and can enable attacker-controlled commands and malware execution through a legitimate Windows management application. Observed campaigns deployed stealers and backdoors, including Rhadamanthys, SilentPrism, and DarkWisp, enabling credential theft, sensitive-data exfiltration, persistence, and remote command execution. Microsoft classifies the vulnerability as a local security feature bypass, with potentially high confidentiality, integrity, and availability impact. Privilege escalation is not established as an inherent consequence of the flaw.

Mitigation

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

No vendor-specific workaround is identified. Until patching is complete, restrict execution of untrusted Microsoft Saved Console files, particularly for non-administrative users, and limit their delivery through email, messaging, and web downloads. Monitor MMC launches for anomalous directory spacing, suspicious console parameters, unexpected child processes, and outbound payload retrieval. These measures reduce exposure or support detection but do not replace the security update.

Remediation

Patch, then assume compromise.

Apply the applicable Microsoft Windows security update released on March 11, 2025, or a subsequent cumulative update that includes the fix. Prioritize affected endpoints and servers because exploitation in the wild is confirmed. Specific update package identifiers, the complete affected-version list, and fixed build numbers are not available in the supplied information.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
CVE-2025-26633This repository is a proof-of-concept (PoC) exploit for CVE-2025-26633, a vulnerability in Microsoft Management Console (MMC) that allows remote code execution via malicious .msc files and ActiveX controls. The repository is structured in three stages: - 'stage1/dropper.ps1' is a PowerShell script that creates and writes malicious .msc files to the Windows System32 directory, replacing a placeholder with a URL pointing to a remote HTML payload, and then launches the MMC with the malicious file. - 'stage2/index.html' is an HTML file containing JavaScript that, when loaded in the MMC context with ActiveX enabled, executes arbitrary PowerShell commands. The default action is to launch calc.exe, but commented lines show how it could download and execute further PowerShell payloads or kill processes. - 'stage3/shell.ps1' is a PowerShell script that downloads a remote executable ('shell.exe') from a specified IP address and runs it. The exploit demonstrates the attack chain from initial file drop to remote code execution, with clear network and file system indicators. The PoC is intended for educational and research purposes only.sandsoncosta · Disclosed Apr 8, 2025 · powershell · html · local · networkPoCMSC-EvilTwin-Local-Privilege-EscalationThis repository contains a proof-of-concept exploit for CVE-2025-26633, a local privilege escalation vulnerability in Microsoft Management Console (MMC) on Windows systems. The main file, 'CVE-2025-26633_mmc_addadmin.py', generates a malicious .msc (MMC snap-in) file that, when opened with mmc.exe on a vulnerable Windows system, executes an embedded PowerShell command. This command creates a new local administrator account ('hacker'/'P@ssw0rd123!') silently. The exploit targets unpatched Windows 10, Windows 11, and Windows Server 2016-2025 systems prior to the March 2025 security updates. The attack vector is local, requiring the attacker to convince a user to open the crafted .msc file. The repository includes a README with detailed vulnerability and usage information, and a GPL license file. No network endpoints or remote services are involved; the exploit is purely local and post-exploitation in nature.mbanyamer · Disclosed Nov 22, 2025 · python · localPoC
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 1507operating_system
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows Server 2008operating_system
Microsoft CorporationWindows Server 2008 R2operating_system
Microsoft CorporationWindows Server 2008 Sp2operating_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
FAQ

Frequently asked questions

Is CVE-2025-26633 exploited in the wild?
Yes. As of Nov 4, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Mar 11, 2025.
Is there a public exploit for CVE-2025-26633?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2025-26633, the earliest disclosed Apr 8, 2025.
Is there a patch for CVE-2025-26633?
Apply the applicable Microsoft Windows security update released on March 11, 2025, or a subsequent cumulative update that includes the fix. Prioritize affected endpoints and servers because exploitation in the wild is confirmed.
What products are affected by CVE-2025-26633?
Microsoft Corporation Windows 10 1507, Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, and 14 more.
How severe is CVE-2025-26633?
CVE-2025-26633 has a CVSS v3.1 score of 7.0 (High) and an EPSS score of 30.4% (98th percentile) as of Nov 4, 2026.
Mallory platform

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, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence7Every report linking this CVE to a named adversary.
Associated malware18Malware families linked to this CVE, with evidence and IOCs.
Detection signatures3YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity31Community discussion across Reddit, Mastodon, and other social sources.