Skip to main content
Mallory
HighPublic exploitVulnerability

CVE-2026-50656: RoguePlanet

Published Jun 16, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days2 mentions · peak 1 in a dayToday
CVSS7.0High · v3.1
EPSS11.2%96th percentile
CISA KEVNoNot listed
In the wildReported5 exploitation records in Mallory
Vendor
Microsoft Corporation
IdentifiersCVE-2026-50656CWE-59 · Improper Link Resolution Before…

RoguePlanet (CVE-2026-50656) is a local elevation-of-privilege vulnerability in the Microsoft Malware Protection Engine used by Microsoft Defender. Improper link resolution before file access, combined with a race condition in Defender file handling, allows a low-privileged local attacker to redirect privileged filesystem operations and obtain NT AUTHORITY\SYSTEM privileges. The original exploitation technique involved a virtual disk. Publicly disclosed in June 2026, the vulnerability received an initial engine update in July 2026. ShieldBreak, separately tracked as CVE-2026-69414, subsequently bypassed that fix.

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 elevates a standard local user to SYSTEM, compromising the affected Windows system's security boundary. SYSTEM-level execution permits access to protected data, modification of system resources, interference with endpoint protections, and installation of privileged persistence. This is a local privilege-escalation vulnerability, not a standalone remote initial-access vector.

Mitigation

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

Restrict untrusted local code execution, including through AppLocker or Windows Defender Application Control allowlisting, to reduce opportunities to run privilege-escalation tools. Limit unnecessary local access and monitor suspicious filesystem redirection associated with Defender remediation. These are defense-in-depth measures; no RoguePlanet-specific vendor workaround is identified.

Remediation

Patch, then assume compromise.

Update Microsoft Defender's Malware Protection Engine to the latest available version and verify that engine updates are being installed successfully. Version 1.1.26060.3008 was released in July 2026 to address RoguePlanet, but ShieldBreak subsequently bypassed that fix. Version 1.1.26080.3 addressed ShieldBreak in September 2026; use that version or later rather than relying solely on the original RoguePlanet update. Engine updates normally install automatically. Subsequent ShieldCrash bypass claims do not establish that the original RoguePlanet exploit remains effective against current engines.

Public exploits

Exploits

2 exploits validated by Mallory's analysis. Hidden: 6 rejected by Mallory's analysis as not a working exploit.

View more in app →
CVE-2026-50656This repository is a Windows-focused local exploit PoC for CVE-2026-50656, described as a Microsoft Defender patch bypass ('ShieldBreak'). The repo is small and centered around a single substantial C++ source file, ShieldBreak-MSNightmare/ShieldBreak.cpp, plus Visual Studio project files, a resource header, and documentation. The top-level README mainly wraps and references the upstream ShieldBreak project, while the nested ShieldBreak-MSNightmare directory contains the actual exploit implementation. The exploit is not a framework module and appears to be a standalone Visual Studio C++ application. Its code imports numerous Windows-specific APIs and libraries including ntdll, Cloud Files API (cfapi), COM/OLE, ACL APIs, and Task Scheduler interfaces. The visible code shows embedded resources for a ZIP and DLL, suggesting the executable carries staged artifacts internally. Project metadata further references eicar_com.zip, Report.wer, ShellDll.dll, and Warden.dll, indicating the exploit likely uses a Defender-detectable sample plus one or more DLL payloads and a crafted WER report. Operationally, the exploit appears to be a local attack chain rather than a remote/network exploit. It creates files and directories, interacts with Cloud Files sync-root functionality, sets up a named pipe for synchronization, and uses COM to connect to the Windows Task Scheduler service. It specifically opens the task folder '\Microsoft\Windows\Windows Error Reporting', retrieves the 'QueueReporting' task, and runs it. This strongly suggests the exploit abuses Windows Error Reporting task execution as part of the bypass chain. After successful execution it prints '[+] Exploit succeeded.' and performs cleanup by disconnecting/unregistering the sync root and deleting staged files/directories. No external network C2, hardcoded IPs, or remote URLs are present in the exploit code shown. The notable fingerprintable targets are local Windows components: the Windows Error Reporting scheduled task path, temporary/staged files, embedded DLL/ZIP resources, and named-pipe-based IPC. Overall, this is a real exploit PoC with embedded payload/staging capability, intended to demonstrate a local Defender bypass on modern Windows systems rather than merely detect the vulnerability.HORKimhab · Disclosed Aug 12, 2026 · cpp · xml · localOperationalshieldbreakShieldBreak is a standalone Visual Studio C++20 console project, not a known exploitation framework module. Its primary implementation is ShieldBreak.cpp (about 47 KB); the remaining listed files are Visual Studio solution/project metadata, a resource-ID header, README, and license. The project is configured for Win32 and x64 Debug/Release builds and links against ntdll, CldApi, onecore, and Task Scheduler libraries. The source defines Microsoft Defender-related internal data types and uses Windows Cloud Files APIs, COM Task Scheduler interfaces, Windows Error Reporting task execution, resource extraction, and a named pipe. It embeds or expects ZIP and DLL resources and cleans up the synchronization root, WER files/directories, scan target, and pipe after execution. No remote host, URL, IP address, DNS name, or external C2 endpoint is present in the supplied code. The project metadata references ShieldBreak.rc plus several binary/resource inputs that are absent from the eight-file listing, meaning the repository as provided may not build without those missing artifacts. The README attributes the technique to CVE-2026-50656 and claims a Defender patch bypass, but the claim and the behavior of the unavailable embedded DLL cannot be independently verified from the supplied contents.cpp · xml · localOperational
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 CorporationMalware Protection Engineapplication
FAQ

Frequently asked questions

Is CVE-2026-50656 exploited in the wild?
Yes. As of Nov 19, 2026, Mallory has reports of exploitation in the wild.
Is there a public exploit for CVE-2026-50656?
Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-50656, the earliest disclosed Aug 12, 2026.
Is there a patch for CVE-2026-50656?
Update Microsoft Defender's Malware Protection Engine to the latest available version and verify that engine updates are being installed successfully. Version 1.1.26060.3008 was released in July 2026 to address RoguePlanet, but ShieldBreak subsequently bypassed that fix.
What products are affected by CVE-2026-50656?
Microsoft Corporation Malware Protection Engine.
How severe is CVE-2026-50656?
CVE-2026-50656 has a CVSS v3.1 score of 7.0 (High) and an EPSS score of 11.2% (96th percentile) as of Nov 19, 2026.
Activity feed

Recent activity

261 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
thecyberexpress com vulnerabilitiesNews · Nov 13, 2026SignDrop Zero-Day Exploit Abuses CLFS To Gain AccessA previously disclosed vulnerability associated with MSNightmare's Windows and Defender research, mentioned as background. Microsoft confirmed it in June and patched it in July. The content does not describe its technical mechanism or specifically establish exploitation in attacks.Read more ↗the hacker newsNews · Nov 12, 2026New SignDrop Zero-Day Exploit Turns Windows CLFS Security Feature Into SYSTEM AccessAn earlier Microsoft Defender vulnerability associated with the researcher's RoguePlanet exploit, mentioned as background. Microsoft confirmed it in June and patched it in July. The article characterizes the earlier Defender exploits collectively as targeting race conditions in file handling.Read more ↗uganda certNews · Oct 6, 2026Microsoft Officially Assigns CVE to ShieldBreak Zero-Day as Patch Development Confirmed (CVE-2026-69414) | Uganda National Computer Emergency Response Team-National CertThe underlying RoguePlanet vulnerability addressed by the August 2026 Patch Tuesday updates. ShieldBreak reportedly bypasses its patch. The content recommends applying August cumulative updates to address RoguePlanet but does not separately explain its technical mechanism.Read more ↗computerbase securityNews · Sep 11, 2026Patch vom Patch geknackt: Microsoft Defender hat erneut ein Zero-Day-Problem - ComputerBaseA local privilege-escalation vulnerability in Microsoft Malware Protection Engine, publicly disclosed in June 2026 and patched in July. ShieldBreak subsequently bypassed that patch.Read more ↗
+65 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
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 evidence1Every report linking this CVE to a named adversary.
Associated malware7Malware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity131Community discussion across Reddit, Mastodon, and other social sources.