Skip to main content
Mallory
HighCISA KEVExploited in the wildPublic exploit

MSC EvilTwin

IdentifiersCVE-2025-26633CWE-707· Improper Neutralization

CVE-2025-26633 is a Microsoft Management Console (MMC) security feature bypass vulnerability, described by Microsoft as improper neutralization in MMC that allows an unauthorized attacker to bypass a security feature locally. Public reporting and threat research refer to the issue as "MSC EvilTwin." The vulnerability is exploited through malicious .msc console files and appears to involve MMC’s handling of localized console resources and MUIPath resolution, where a benign console can trigger loading of a rogue counterpart from an attacker-controlled path such as an en-US directory. Multiple reports also describe related path-manipulation and trailing-space directory tricks used in exploitation chains. In observed attacks, opening the crafted .msc file causes mmc.exe to load attacker-controlled content and execute follow-on PowerShell or loader logic, enabling malware delivery. Microsoft reported exploitation in the wild at disclosure, and third-party reporting indicates functional exploit code exists.

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 bypasses MMC security controls intended to prevent unsafe console content from executing as trusted content. In real-world campaigns, this has been used to execute attacker-controlled code via malicious .msc files, leading to malware installation and full compromise of the affected host. Reported post-exploitation outcomes include deployment of loaders and backdoors, credential and data theft, persistence establishment, command-and-control access, lateral movement, and ransomware deployment. Although Microsoft classifies the bug as a security feature bypass, operationally it has enabled arbitrary code execution chains in the context of the user opening the malicious file.

Mitigation

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

If immediate patching is not possible, reduce exposure by blocking or tightly restricting execution of .msc files for non-administrative users, preventing delivery of .msc and disguised installer payloads through email, chat, and web downloads, and hardening application control policies so only approved MMC consoles can run. Monitor for suspicious mmc.exe executions, especially launches involving unusual command-line parameters, MUIPath manipulation, en-US resource-path abuse, anomalous spaces in Windows or Program Files paths, and child PowerShell or script execution. Additional defensive measures supported by the content include monitoring for newly created .msc files, suspicious scheduled tasks, registry persistence changes, and outbound connections following mmc.exe execution. User-awareness controls against phishing and fake IT-support lures are also relevant because exploitation commonly depends on social engineering.

Remediation

Patch, then assume compromise.

Apply Microsoft's March 2025 security updates for all affected Windows client and server versions and ensure systems are updated to fixed builds. The content identifies the following fixed version thresholds: Windows 10 1809 / Server 2019 < 10.0.17763.7009, Server 2022 < 10.0.20348.3328, Windows 10 21H2 < 10.0.19044.5608, Windows 10 22H2 < 10.0.19045.5608, Windows 11 22H2 < 10.0.22621.5039, Windows 11 23H2 < 10.0.22631.5039, Windows 11 24H2 / Server 2025 < 10.0.26100.3476, Server 2016 < 10.0.14393.7876, Server 2012 < 6.2.9200.25368, Server 2012 R2 < 6.3.9600.22470, Server 2008 SP2 < 6.0.6003.23168, and Server 2008 R2 SP1 < 6.1.7601.27618. Prioritize patching internet-exposed, user-workstation, jump-host, and high-risk administrative systems, especially where users can receive phishing lures or untrusted files.
PUBLIC EXPLOITS

Exploits

2 valid exploits after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).

VALID 2 / 3 TOTALView more in app
MSC-EvilTwin-Local-Privilege-EscalationMaturityPoCVerified exploit

This 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.

mbanyamerDisclosed Nov 22, 2025pythonlocal
CVE-2025-26633MaturityPoCVerified exploit

This 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.

sandsoncostaDisclosed Apr 8, 2025powershellhtmllocalnetwork
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

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 evidence4

Every observed campaign linking this CVE to a named adversary.

Associated malware12

Malware families riding this exploit, with evidence and IOCs.

Detection signatures2

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 activity30

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