MiniPlasma: Chaotic Eclipse PoC turns the 2020 Windows Cloud Files driver flaw CVE-2020-17103 into a SYSTEM shell on patched Windows 11; June 2026 updates fix it
MiniPlasma revived Windows Cloud Files flaw CVE-2020-17103 for a SYSTEM shell; Microsoft's June 2026 updates fix it
Analysis
Chaotic Eclipse, also known as Nightmare Eclipse, released source code and a compiled exploit for MiniPlasma on GitHub, saying that the flaw James Forshaw of Google Project Zero reported in September 2020 in the HsmOsBlockPlaceholderAccess routine of the Cloud Filter driver cldflt.sys, assigned CVE-2020-17103 and reportedly fixed in December 2020, was still present and that Google's original proof of concept worked unchanged (BleepingComputer, 2026-05-17). The exploit appears to abuse how the driver handles registry key creation through the undocumented CfAbortHydration API, which Forshaw's report said could create arbitrary registry keys in the .DEFAULT user hive without proper access checks (BleepingComputer, 2026-05-17). BleepingComputer, using a standard user account on a fully patched Windows 11 Pro system with the May 2026 updates, got a command prompt with SYSTEM privileges, and Will Dormann confirmed the exploit on the latest public Windows 11 but not on the latest Insider Preview Canary build (BleepingComputer, 2026-05-17); the researcher says success may vary because it is a race condition and that all Windows versions are likely affected (The Hacker News, 2026-05-18).
Microsoft re-released CVE-2020-17103 on 2026-06-09 to comprehensively address the flaw "recently publicly referred to as 'Mini-Plasma'" and recommends installing the June 2026 Windows updates; it rates it Important with a CVSS 3.1 base score of 7.0 and lists it as not exploited (Microsoft MSRC, CVE-2020-17103). MiniPlasma is the latest in a 2026 series from the same researcher after BlueHammer, RedSun and the UnDefend tool, all three of which were later seen exploited in attacks, and the YellowKey and GreenPlasma exploits (BleepingComputer, 2026-05-17).
Cited evidence
BleepingComputer tested the exploit on a fully patched Windows 11 Pro system running the latest May 2026 Patch Tuesday updates.
Forshaw's original report said that the flaw could allow arbitrary registry keys to be created in the .DEFAULT user hive without proper access checks, potentially enabling privilege escalation.
To comprehensively address the vulnerability identified by CVE-2020-17103 and recently publicly referred to as "Mini-Plasma" Microsoft recommends installing the June 2026 updates for your Windows operating systems.
Updates1
Microsoft rates CVE-2020-17103 at CVSS 3.1 7.0, not 7.8, and re-released it on 2026-06-09, recommending the June 2026 Windows updates to comprehensively address the flaw now called Mini-Plasma, so it is no longer unpatched (Microsoft MSRC, CVE-2020-17103). The reproduction on fully patched Windows 11 Pro with the May 2026 updates was BleepingComputer's own test with a standard user account, and Will Dormann confirmed it separately on the latest public Windows 11 (BleepingComputer, 2026-05-17). MiniPlasma is not the third proof of concept in the series: BlueHammer, RedSun and UnDefend came first, followed by YellowKey and GreenPlasma (BleepingComputer, 2026-05-17). The monitoring the reporting gives is ThreatLocker's pair of registry paths; no source advises driver-load monitoring or says that disabling Cloud Files or OneDrive integration removes the attack surface (BleepingComputer, 2026-05-17).
Sources3
Revision history
- Published 2026-05-19-2505c918
- Correction 2026-10-21T1148Z-audit
Microsoft scores CVE-2020-17103 CVSS 3.1 7.0, not 7.8, and re-released it on 2026-06-09 with the June 2026 Windows updates as the fix for MiniPlasma, so the flaw is patched rather than unpatched. BleepingComputer tested the exploit itself on Windows 11 Pro with the May 2026 updates, and Will Dormann separately confirmed it on the latest public Windows 11. MiniPlasma follows BlueHammer, RedSun, UnDefend, YellowKey and GreenPlasma in the researcher's 2026 series rather than being its third proof of concept, and the monitoring advice is ThreatLocker's two registry paths.
Changed: affected_products body classification cves event_date evidence headline sectors 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.