Windows Defender Patch for RoguePlanet Zero-Day Vulnerability May Exhaust Disk Space on Windows Systems
Microsoft has issued a patch for a critical zero-day vulnerability known as RoguePlanet (CVE-2026-50656) affecting the Microsoft Malware Protection Engine that powers Windows Defender. However, security researcher NightmareEclipse, who originally discovered and disclosed the flaw, warns that the fix itself may cause Windows systems to exhaust all available disk space by writing massive files to the drive.
The vulnerability first gained attention in June when NightmareEclipse published technical details and a working exploit. According to the researcher, RoguePlanet enabled remote attackers to obtain full administrative control over both Windows 10 and Windows 11 even when real-time protection was turned off. In response, Microsoft released an update to the Microsoft Malware Protection Engine component, which is designed to install automatically without requiring user intervention. The company also added additional defensive measures alongside the fix.
Shortly after the patch deployment, NightmareEclipse reported that the update can trigger unintended behavior in which Defender writes enormous volumes of data to disk. The issue is linked to the mpengine.dll library and the SpyNet functions that attempt to locally cache the Zone.Identifier alternate data stream — a Windows metadata mechanism used to track file origin information such as downloads from the internet.
Under normal circumstances, Windows Defender enforces strict size limits on files it creates during scanning and quarantine operations. However, the researcher claims that Zone.Identifier streams are treated as an exception, allowing Defender to store them locally regardless of their size. An attacker can exploit this by setting up a specially crafted SMB server that delivers a malicious file accompanied by an extremely large Zone.Identifier stream while keeping the connection alive. This can cause Defender to hang during processing and consume all remaining free space on the system drive.
While the computer may not crash immediately, a Windows system with a completely full disk tends to exhibit erratic behavior: applications and system services may fail unpredictably, similar to an overloaded server. Microsoft has not yet confirmed or commented on the reported disk-exhaustion issue at the time of publication. The ongoing dispute between the company and NightmareEclipse has lasted several months, with the researcher criticizing Microsoft for inadequate recognition and compensation for discovered vulnerabilities, while the company has expressed concerns about the early public disclosure of exploits before patches were available.
Related articles
Exploiting CVE-2025-55182 React2Shell Vulnerability on Hack The Box Reactor Machine
A detailed walkthrough demonstrates remote code execution against a seasonal Hack The Box machine named Reactor by abusing the critical Next.js deserialization flaw CVE-2025-55182, also known as React2Shell. The attack begins with Nmap reconnaissance revealing an exposed Next.js service on port 3000, followed by Wappalyzer identification of an outdated framework version. Public exploit code is used to obtain an initial reverse shell as the node user without authentication. Credential access is achieved by extracting password hashes from the reactor.db SQLite database and cracking the engineer account with Hashcat against rockyou.txt. Privilege escalation leverages an exposed Node.js Inspector debug port on 9229, allowing WebSocket interaction via websocat to set the SUID bit on /bin/bash and obtain root access. The article highlights both the impact of the unauthenticated RCE vulnerability and common misconfigurations such as forgotten debug ports on production systems.
CISA Adds MikroTik RouterOS Flaws CVE-2026-67277 and CVE-2026-86060 to Known Exploited Vulnerabilities Catalog
The US Cybersecurity and Infrastructure Security Agency has added two actively exploited vulnerabilities in MikroTik RouterOS to its Known Exploited Vulnerabilities Catalog. CVE-2026-86060 stems from improper sanitization of command argument delimiters and can lead to privilege escalation after an attacker gains access to the SSH login helper and alters trusted policy masks. CVE-2026-67277 involves missing authentication checks in critical RouterOS functions, allowing connections before authentication completes and potentially leaking kernel memory or causing denial-of-service conditions. CISA directed US federal agencies to apply mitigations by September 13 and specifically investigate any signs of compromise related to CVE-2026-86060. The agency noted that the flaws carry broader exploitation risk and urged all organizations using affected MikroTik products to take immediate action.
The Birth of CVE: How Two MITRE Engineers Built the Universal Vulnerability Identifier in 1999
In the late 1990s, security teams faced chaos with one vulnerability carrying dozens of incompatible names across scanners, IDS tools, and CERT advisories. Two MITRE engineers, David E. Mann and Steven M. Christey, proposed a minimal Common Vulnerabilities and Exposures list to solve correlation problems without imposing taxonomy or risk models. Their January 1999 paper led to a Purdue workshop, the formation of the CVE Editorial Board, and a public launch on September 29, 1999, with 321 initial entries. The design deliberately avoided ownership by any vendor and kept names as simple CVE-year-number strings. This neutral, open approach allowed competing vendors to map their proprietary databases to a shared reference without agreeing on classifications. The same minimalist philosophy later influenced NVD, OSV, and GitHub Advisory Database.
OnePlus 13R Preinstalled Account App Leaks Cloud Session Tokens to Any App Declaring Required Permission
Researchers at Doyensec identified a vulnerability in the preinstalled com.oneplus.account application on the OnePlus 13R that allows any third-party app to steal a valid OnePlus Cloud session token. The flaw stems from the OPAccountProvider component lacking the protectionLevel="signature" attribute on its declared permission com.oneplus.account.READ_ACCOUNT_INFO, enabling any app to request the permission and query the provider directly. Once obtained, the token grants access to OnePlus Cloud APIs without further user interaction or warnings. Doyensec responsibly disclosed the issue on 30 December 2025, leading OnePlus to acknowledge the high-severity problem and pay a $720 bounty in March 2026. Follow-up testing in September on firmware CPH2691_16.0.10.500(EX01) confirmed the token leakage persists, although full account takeover via the regional API was no longer reproducible for US and EMEA accounts due to backend changes. Users are advised to avoid untrusted apps and apply future updates, while OnePlus needs only to add the signature protection level to close the exposure.