Microsoft calls Nightmare Eclipse's six uncoordinated Windows zero-day releases "never justifiable"; the three May drops were fixed in June 2026
Microsoft says its Digital Crimes Unit will keep bringing cases after six leaked Windows zero-days; three fixed in June
Analysis
In a blog post on 2026-05-27, the Microsoft Security Response Center said the vulnerabilities known as RedSun, UnDefend, BlueHammer, YellowKey, GreenPlasma and MiniPlasma "were not responsibly disclosed" and that uncoordinated disclosures putting proof-of-concept code for unpatched flaws "into the hands of bad actors are never justifiable"; it added that its Digital Crimes Unit "will continue bringing cases against these actors and those that enable their criminal activity" (Microsoft MSRC blog, 2026-05-27). The Record reported the post on 2026-05-29 as Microsoft's first response to the release campaign, noted that the researcher's GitHub account had since been removed, and reported that the researcher threatened a further release on 14 July 2026, the date of Microsoft's July Patch Tuesday (The Record, 2026-05-29).
Contradiction: the outlets read the statement differently. The Record says Microsoft "stopped short of directly threatening legal action" (The Record, 2026-05-29), while heise writes that the company "is threatening lawsuits and the police" (heise Security, 2026-05-29).
The first three drops, BlueHammer (CVE-2026-33825), UnDefend (CVE-2026-45498) and RedSun (CVE-2026-41091), all disclosed in April, have been exploited in live intrusions and appear on CISA's Known Exploited Vulnerabilities catalogue (The Record, 2026-05-29); UnDefend lets a standard user block Microsoft Defender definition updates (BleepingComputer, 2026-06-10). The three May drops had no patch and no confirmed exploitation when The Record reported (The Record, 2026-05-29). YellowKey, tracked as CVE-2026-45585, is a BitLocker security feature bypass that needs physical access (Microsoft MSRC). The researcher says MiniPlasma abuses the HsmOsBlockPlaceholderAccess routine of the Cloud Filter driver cldflt.sys, and that it is the flaw Google Project Zero reported in 2020 as CVE-2020-17103, "still present, unpatched"; BleepingComputer's test on a fully patched Windows 11 Pro system with the May 2026 updates opened a SYSTEM command prompt from a standard user account (BleepingComputer, 2026-05-17).
Microsoft fixed the three May drops on 2026-06-09: GreenPlasma as CVE-2026-45586, a CTFMON elevation of privilege that can give SYSTEM (MSRC CVE-2026-45586), MiniPlasma by re-releasing CVE-2020-17103 with the June 2026 updates (MSRC CVE-2020-17103), and YellowKey in the same Patch Tuesday (BleepingComputer, 2026-06-10).
Cited evidence
Our Digital Crimes Unit will continue bringing cases against these actors and those that enable their criminal activity
The company stopped short of directly threatening legal action
The researcher threatened a further release on July 14
The company is threatening lawsuits and the police.
This CVE has been re-released to comprehensively address the vulnerability identified by CVE-2020-17103
Updates1
Microsoft fixed the three May drops in the June 2026 Patch Tuesday updates of 2026-06-09: YellowKey (CVE-2026-45585) and GreenPlasma, now tracked as CVE-2026-45586 (BleepingComputer, 2026-06-10), and MiniPlasma through CVE-2020-17103, which Microsoft re-released "to comprehensively address the vulnerability identified by CVE-2020-17103" (MSRC CVE-2020-17103). BleepingComputer also reports that Microsoft backtracked on its initial threats of legal action after blowback on social media, saying it would work with law enforcement when a security researcher "breaks the law and engages in malicious activity causing real harm to our customers" (BleepingComputer, 2026-06-10).
Sources8
Revision history
- Published 2026-05-30-aca445cc
- Update 2026-10-21T1149Z-audit
Microsoft fixed YellowKey, GreenPlasma (now CVE-2026-45586) and MiniPlasma (through a re-release of CVE-2020-17103) in the June 2026 updates and, according to BleepingComputer, stepped back from its initial legal threats. Microsoft's statement is now dated to its 2026-05-27 blog post, the headline no longer says criminal action was threatened and the differing readings by The Record and heise are shown, the 14 July release is placed on the July Patch Tuesday, and YellowKey's CVE is described as a physical-access BitLocker bypass rather than a local privilege escalation; uncited detection advice is removed.
Changed: affected_products body classification cves event_date evidence headline references sources sourcing_note summary tags techniques title
AI-generated · no human review · this permalink is the shareable record for the finding · verify operationally critical claims against the linked primary source.