CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

Nightmare Eclipse Windows zero-day series

campaign · campaign:nightmare-eclipse-microsoft-dcu-threat-greenplasma-miniplasmaaac

Nightmare Eclipse's 2026 public Windows zero-day drop series. YellowKey (BitLocker security feature bypass, CVE-2026-45585), GreenPlasma (CTFMON elevation of privilege, CVE-2026-45586) and MiniPlasma (cldflt.sys SYSTEM escalation, addressed by the re-released CVE-2020-17103) were all fixed in the 2026-06-09 Windows updates. Microsoft's MSRC called uncoordinated disclosure never justifiable on 2026-05-27, and the persona threatened a further release for 14 July 2026.

Coverage
6
first 2026-05-15 → last 2026-10-21
Latest activity
2026-10-21
Microsoft says its Digital Crimes Unit will keep bringing cases after six leaked Windows zero-days; three…
Peak priority
high
2 high · 3 notable · 1 routine
Targets
public-sector
sectors: public-sector, energy, water · regions: switzerland
Sources cited
21
10 hosts
2026-05-156 appearances2026-07-09

Action items (1)

Do-now tasks recorded on the entries about Nightmare Eclipse Windows zero-day series, newest first. Check the date before acting on an older one.

  • On WSUS-gated, air-gapped, offline or OT-adjacent Windows estates where Defender engine updates are deferred or pinned, verify the installed Malware Protection Engine build is ≥ 1.1.26080.3, which also closes the ShieldBreak bypass (CVE-2026-69414) of this fix, rather than assuming auto-update reached it.
    2026-07-09CVE-2026-50656

Defender insights

What each entry about Nightmare Eclipse Windows zero-day series tells a defender to do, newest first.

2026-05-30NOTABLEexploitedMicrosoft says its Digital Crimes Unit will keep bringing cases after six leaked Windows zero-days; three fixed in June

Exposure · detection

2026-05-15NOTABLELeaked BitLocker bypass "YellowKey" and CTFMON privilege escalation "GreenPlasma" were fixed in the June 2026 updates

Exposure · detection

2026-07-09ROUTINEMicrosoft ships the engine fix for RoguePlanet (CVE-2026-50656), the Defender SYSTEM-level LPE NCSC-CH has tracked with a public PoC since June

Exposure

2026-05-19NOTABLEMiniPlasma revived Windows Cloud Files flaw CVE-2020-17103 for a SYSTEM shell; Microsoft's June 2026 updates fix it

Exposure · detection

Relationships explore in graph

Typed, source-stated connections from the entity registry; each edge cites the entry whose reporting establishes it.

attributed to

exploits

Story timeline

  1. 2026-07-09CVE-2026-50656: Microsoft Defender engine 'RoguePlanet' local privilege escalation now patched; NCSC-CH tracks the ongoing 'Nightmare Eclipse' zero-day series
    trending-vulnerabilitiesMicrosoft ships the engine fix for RoguePlanet (CVE-2026-50656), the Defender SYSTEM-level LPE NCSC-CH has tracked with a public PoC since June
  2. 2026-06-12"GreatXML": unpatched BitLocker bypass via crafted XML on the recovery partition, PoC public, practical severity contested
    active-threats
  3. 2026-06-11"RoguePlanet" Microsoft Defender zero-day: TOCTOU race in the scan engine yields a SYSTEM shell, no CVE, no patch
    active-threats
  4. 2026-05-30Microsoft calls Nightmare Eclipse's six uncoordinated Windows zero-day releases "never justifiable"; the three May drops were fixed in June 2026
    trending-vulnerabilitiesMicrosoft says its Digital Crimes Unit will keep bringing cases after six leaked Windows zero-days; three fixed in June
  5. 2026-05-19MiniPlasma: 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
    trending-vulnerabilitiesMiniPlasma revived Windows Cloud Files flaw CVE-2020-17103 for a SYSTEM shell; Microsoft's June 2026 updates fix it
  6. 2026-05-15Windows BitLocker "YellowKey" (CVE-2026-45585) and CTFMON "GreenPlasma" (CVE-2026-45586) zero-days: public PoCs in May, fixed in the June 2026 Windows updates
    active-threatsLeaked BitLocker bypass "YellowKey" and CTFMON privilege escalation "GreenPlasma" were fixed in the June 2026 updates
ATT&CK techniques (7 across 6 tactics)

7 techniques observed across 6 entries about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)

  • ExecutionCommand and Scripting Interpreter: Windows Command Shell
  • PersistenceModify Registry · Pre-OS Boot · Pre-OS Boot: System Firmware
  • Privilege EscalationExploitation for Privilege Escalation
  • StealthPre-OS Boot · Pre-OS Boot: System Firmware
  • Defense ImpairmentModify Registry · Disable or Modify Tools
  • CollectionData from Local System

Execution TA0002

T1059.003Command and Scripting Interpreter: Windows Command Shell×1

Adversaries may abuse the Windows command shell for execution. The Windows command shell (cmd) is the primary command prompt on Windows systems. The Windows command prompt can be used to control almost any aspect of a system, with various permission levels required for different subsets of commands. The command prompt can be invoked remotely via Remote Services such as SSH.

Evidence: 2026-05-15/windows-bitlocker-yellowkey-and-ctfmon-greenplasma-zero-days · ATT&CK page ↗

Persistence TA0003

T1112Modify Registry×1

Adversaries may interact with the Windows Registry as part of a variety of other techniques to aid in defense evasion, persistence, and execution.

Evidence: 2026-05-19/chaotic-eclipse-windows-zero-days-miniplasma-is-third-poc-in · ATT&CK page ↗

T1542Pre-OS Boot×1

Adversaries may abuse Pre-OS Boot mechanisms as a way to establish persistence on a system. During the booting process of a computer, firmware and various startup services are loaded before the operating system. These programs control flow of execution before the operating system takes control.

Evidence: 2026-06-12/greatxml-unpatched-bitlocker-bypass-via-crafted-xml-on-the-r · ATT&CK page ↗

T1542.001Pre-OS Boot: System Firmware×1

Adversaries may modify system firmware to persist on systems.The BIOS (Basic Input/Output System) and The Unified Extensible Firmware Interface (UEFI) or Extensible Firmware Interface (EFI) are examples of system firmware that operate as the software interface between the operating system and hardware of a computer.

Evidence: 2026-06-12/greatxml-unpatched-bitlocker-bypass-via-crafted-xml-on-the-r · ATT&CK page ↗

Privilege Escalation TA0004

T1068Exploitation for Privilege Escalation×5

Adversaries may exploit software vulnerabilities in an attempt to elevate privileges. Exploitation of a software vulnerability occurs when an adversary takes advantage of a programming error in a program, service, or within the operating system software or kernel itself to execute adversary-controlled code. Security constructs such as permission levels will often hinder access to information and use of certain techniques, so adversaries will likely need to perform privilege escalation to include use of software exploitation to circumvent those restrictions.

Evidence: 2026-07-09/ncsc-ch-rogueplanet-cve-2026-50656-defender-lpe-fixed · 2026-06-11/rogueplanet-microsoft-defender-zero-day-toctou-race-in-the-s · 2026-05-30/nightmare-eclipse-chaotic-eclipse-microsoft-s-digital-crimes · 2026-05-19/chaotic-eclipse-windows-zero-days-miniplasma-is-third-poc-in · 2026-05-15/windows-bitlocker-yellowkey-and-ctfmon-greenplasma-zero-days · ATT&CK page ↗

Stealth TA0005

T1542Pre-OS Boot×1

Adversaries may abuse Pre-OS Boot mechanisms as a way to establish persistence on a system. During the booting process of a computer, firmware and various startup services are loaded before the operating system. These programs control flow of execution before the operating system takes control.

Evidence: 2026-06-12/greatxml-unpatched-bitlocker-bypass-via-crafted-xml-on-the-r · ATT&CK page ↗

T1542.001Pre-OS Boot: System Firmware×1

Adversaries may modify system firmware to persist on systems.The BIOS (Basic Input/Output System) and The Unified Extensible Firmware Interface (UEFI) or Extensible Firmware Interface (EFI) are examples of system firmware that operate as the software interface between the operating system and hardware of a computer.

Evidence: 2026-06-12/greatxml-unpatched-bitlocker-bypass-via-crafted-xml-on-the-r · ATT&CK page ↗

Defense Impairment TA0112

T1112Modify Registry×1

Adversaries may interact with the Windows Registry as part of a variety of other techniques to aid in defense evasion, persistence, and execution.

Evidence: 2026-05-19/chaotic-eclipse-windows-zero-days-miniplasma-is-third-poc-in · ATT&CK page ↗

T1685Disable or Modify Tools×1

Adversaries may disable, degrade, or tamper with security tools or applications (e.g., endpoint detection and response (EDR) tools, intrusion detection systems (IDS), antivirus, logging agents, sensors, etc.) to impair or reduce visibility of defensive capabilities. This may include stopping specific services, killing processes, modifying or deleting tool configuration files and Registry keys, or preventing tools from updating. This may also include impairing defenses more broadly by disrupting preventative, detection, and response mechanisms across host, network, and cloud environments.

Evidence: 2026-05-30/nightmare-eclipse-chaotic-eclipse-microsoft-s-digital-crimes · ATT&CK page ↗

Collection TA0009

T1005Data from Local System×1

Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.

Evidence: 2026-05-15/windows-bitlocker-yellowkey-and-ctfmon-greenplasma-zero-days · ATT&CK page ↗

Entries about Nightmare Eclipse Windows zero-day series (6)

2026-05-30 · view entry permalink →

NOTABLECVE-2026-45585exploitedupdatedNATOA1

Microsoft calls Nightmare Eclipse's six uncoordinated Windows zero-day releases "never justifiable"; the three May drops were fixed in June 2026

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

Our Digital Crimes Unit will continue bringing cases against these actors and those that enable their criminal activity

Microsoft MSRC blog 2026-05-27

The company stopped short of directly threatening legal action

The researcher threatened a further release on July 14

The Record 2026-05-29

The company is threatening lawsuits and the police.

heise Security 2026-05-29

This CVE has been re-released to comprehensively address the vulnerability identified by CVE-2020-17103

MSRC CVE-2020-17103 2026-06-09
Updaterun 2026-10-21T1149Z-auditaffected_productsbodyclassificationcvesevent_dateevidenceheadlinereferencessourcessourcing_notesummarytagstechniquestitle

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

Builds on: Leaked BitLocker bypass "YellowKey" and CTFMON privilege escalation "GreenPlasma" were fixed in…

vulnerability30 May 05:00Zmulti-sourceOpen finding →

2026-05-15 · view entry permalink →

NOTABLECVE-2026-45585 +1updatedNATOA1

Windows BitLocker "YellowKey" (CVE-2026-45585) and CTFMON "GreenPlasma" (CVE-2026-45586) zero-days: public PoCs in May, fixed in the June 2026 Windows updates

On 2026-05-13 BleepingComputer and The Register reported that the researcher Nightmare Eclipse (also Chaotic Eclipse) had published exploit code for two Windows zero-days, YellowKey and GreenPlasma (BleepingComputer, 2026-05-13) (The Register, 2026-05-13). The researcher's earlier BlueHammer (CVE-2026-33825) and RedSun drops began to be exploited in the wild shortly after release (BleepingComputer, 2026-05-13).

YellowKey is a BitLocker bypass that needs physical access. The researcher says it affects Windows 11 and Windows Server 2022/2025 and works by placing crafted FsTx files on a USB drive or the EFI partition, rebooting into the Windows Recovery Environment (WinRE) and holding CTRL to trigger a shell (BleepingComputer, 2026-05-13). Will Dormann reproduced it with the files on a USB drive but not on the EFI partition: to boot WinRE, Windows replays the NTFS logs in \System Volume Information\FsTx directories on attached drives, the replay deletes X:\Windows\System32\winpeshl.ini, and WinRE then opens CMD.EXE instead of the recovery environment, with the disk still unlocked (BleepingComputer, 2026-05-13). Because it abuses TPM-only automatic unlock, the public exploit works only on the original device, not on a removed drive, and does not work with TPM+PIN (BleepingComputer, 2026-05-13). Microsoft tracks it as CVE-2026-45585, a security feature bypass by physical attack (CWE-77, CVSS 6.8), publicly disclosed and not exploited; its fixed builds are Windows 11 24H2 build 10.0.26100.8655, 25H2 build 10.0.26200.8655, 26H1 build 10.0.28000.2269 and Windows Server 2025 build 10.0.26100.32995, and its product table does not list Windows Server 2022 (MSRC CVE-2026-45585).

Contradiction: the researcher says an unpublished variant also defeats TPM+PIN (BleepingComputer, 2026-05-13); Microsoft states that "if you are using TPM+PIN the vulnerability is not exploitable" (MSRC CVE-2026-45585).

GreenPlasma is a local privilege escalation in CTFMON: an unprivileged user can create arbitrary memory-section objects within directory objects writable by SYSTEM, and the leaked PoC lacks the component needed for a full SYSTEM shell (BleepingComputer, 2026-05-13); in its current state it triggers a UAC consent prompt in default Windows configurations (The Register, 2026-05-13). Microsoft tracks it as CVE-2026-45586, a link-following flaw (CWE-59, CVSS 7.8) in the Windows Collaborative Translation Framework that lets an authorized local attacker gain SYSTEM privileges, released on 2026-06-09 with fixes for Windows 10, Windows 11 and Windows Server 2012 to 2025, publicly disclosed and not exploited (MSRC CVE-2026-45586).

Windows looks for \System Volume Information\FsTx directories on attached drives, and will replay any NTFS logs.

that the YellowKey exploit worked with the FsTx files on a USB drive but could not reproduce the bug using the EFI partition

BleepingComputer 2026-05-13

No, if you are using TPM+PIN the vulnerability is not exploitable.

Added links to June 2026 Windows security updates.

MSRC CVE-2026-45585 2026-05-19

An attacker who successfully exploited this vulnerability could gain SYSTEM privileges.

MSRC CVE-2026-45586 2026-06-09

On Tuesday, Microsoft fixed the GreenPlasma, MiniPlasma, and YellowKey security vulnerabilities as part of its June 2026 Patch Tuesday

BleepingComputer (June 2026 fixes) 2026-06-10
Updaterun 2026-05-20-a0f7b07factionscvessourcesbody

Microsoft formally assigned CVE-2026-45585 to the BitLocker / WinRE bypass disclosed by "Nightmare Eclipse" on 2026-05-12 and confirmed there is still no security update. The MSRC update guide entry, published 2026-05-19, classifies it as CWE-77 (command injection in BitLocker / Windows Recovery Environment), CVSS 6.8 (AV:P/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), with exploit-code maturity rated E:P (proof-of-concept) and remediation level RL:W (workaround only).

Microsoft's interim mitigation, which it recommends that customers "consider implementing" if they are concerned their devices and data are at risk of being compromised or stolen, is per-device work: mount the WinRE image, remove the autofstx.exe entry from the BootExecute registry value inside the WinRE image, commit the image, then re-establish BitLocker trust for WinRE (MSRC CVE-2026-45585). The MSRC FAQ states: "A successful attacker could bypass the BitLocker Device Encryption feature on the system storage device. An attacker with physical access to the target could exploit this vulnerability to gain access to encrypted data."

A pre-boot PIN avoids depending on the WinRE edit: the public exploit relies on TPM-only automatic unlock and does not work with TPM+PIN (BleepingComputer, 2026-05-13), and NCSC-CH advises that BIOS passwords and a BitLocker PIN mitigate the current public PoC (NCSC-CH Security Hub #12574, 2026-05-14).

Updaterun 2026-10-21T1149Z-auditactionsaffected_productsbodyclassificationcvesentitiesevent_dateevidenceheadlineprioritysectorssourcessummarytagstechniquestitle

Microsoft fixed both flaws in the June 2026 Windows updates of 2026-06-09. Revision 2 of the CVE-2026-45585 record "Added links to June 2026 Windows security updates", with fixed builds Windows 11 24H2 build 10.0.26100.8655, 25H2 build 10.0.26200.8655, 26H1 build 10.0.28000.2269 and Windows Server 2025 build 10.0.26100.32995 (MSRC CVE-2026-45585). GreenPlasma received its own identifier, CVE-2026-45586, released the same day with fixes for Windows 10, Windows 11 and Windows Server 2012 to 2025 (MSRC CVE-2026-45586), and BleepingComputer reported that the June 2026 Patch Tuesday fixed GreenPlasma, MiniPlasma and YellowKey (BleepingComputer, 2026-06-10). Before the fix, on 2026-05-21, Microsoft had replaced its manual WinRE steps with a script that removes autofstx.exe from the WinRE BootExecute value and re-seals WinRE so BitLocker trust remains intact (MSRC CVE-2026-45585). Microsoft marks neither flaw as exploited (MSRC CVE-2026-45585) (MSRC CVE-2026-45586).

threat15 May 05:00Zmulti-sourceOpen finding →

2026-07-09 · view entry permalink →

ROUTINECVE-2026-50656updatedNATOA2

CVE-2026-50656: Microsoft Defender engine 'RoguePlanet' local privilege escalation now patched; NCSC-CH tracks the ongoing 'Nightmare Eclipse' zero-day series

NCSC-CH's running tracker on the "Nightmare Eclipse" (aka Chaotic Eclipse) researcher's 2026 zero-day PoC series was updated on 2026-07-09 to record that a CVE has been assigned to RoguePlanet: CVE-2026-50656, a local privilege-escalation vulnerability (CWE-59, improper link resolution before file access / "link following") in the Microsoft Malware Protection Engine that underpins Microsoft Defender, System Center Endpoint Protection and Microsoft Security Essentials (NCSC-CH, 2026-07-09) (Microsoft MSRC, 2026-07-08). The researcher first disclosed RoguePlanet as an unpatched zero-day on 2026-06-09, Patch Tuesday, describing a race condition in Defender that lets a local attacker "execute arbitrary code or spawn a command shell with SYSTEM-level privileges", at which point NCSC-CH logged its status as "Proof of Concept Available, no patch available" (NCSC-CH, 2026-07-09). Microsoft's own record shows the CVE was published 2026-06-16 (CVSS 3.1 7.8, AV:L/AC:L/PR:L/UI:N, rated "Exploitation More Likely", exploitation status "No") and remained without a fix for over three weeks; a revision dated 2026-07-08 confirms Microsoft has now shipped an engine update that closes it: last vulnerable Malware Protection Engine build 1.1.26050.11, first fixed build 1.1.26060.3008 (Microsoft MSRC, 2026-07-08).

NCSC-CH later recorded that a proof of concept dubbed ShieldBreak allegedly bypasses this fix; Microsoft tracks it as CVE-2026-69414 (NCSC-CH, 2026-07-09) and lists engine 1.1.26080.3 as the first build that addresses it (Microsoft Security Response Center, CVE-2026-69414).

Microsoft has released an update to the Microsoft Malware Protection Engine that addresses the vulnerability identified by CVE-2026-50656.

Microsoft is aware of an elevation of privilege in the Microsoft Malware Protection Engine in Microsoft Defender publicly referred to as

Microsoft Security Response Center
Correctionrun 2026-10-11T1307Z-auditreferencesclassificationbodysummarypriorityevidenceactionssources

Neither Microsoft's advisory nor NCSC-CH's tracker describes the exploitation mechanism beyond link following and a race condition, so the earlier triage guidance on symlink races against scanned files and on the engine's child processes is withdrawn. NCSC-CH has since recorded that a proof of concept dubbed ShieldBreak allegedly bypasses this fix, tracked by Microsoft as CVE-2026-69414 (NCSC-CH, 2026-07-09); Microsoft lists engine 1.1.26080.3 as the first build that addresses it (Microsoft Security Response Center, CVE-2026-69414). The priority moves from notable to routine: the flaw is local and the engine fix installs automatically. A pinned estate should therefore verify that build rather than the RoguePlanet fix alone.

Improvementrun 2026-10-21T0800Z-audittitlebody

Microsoft identifies the vulnerable engine as mpengine.dll and says Defender runs on all supported versions of Windows, so every Windows host with Defender enabled was in scope until its engine reached 1.1.26060.3008; hosts with Defender disabled are not in an exploitable state (Microsoft MSRC, 2026-07-08).

Builds on: Nightmare/Chaotic Eclipse zero-day wave; the Defender LPE now carries a CVE, a public PoC, and… · Microsoft has now shipped an engine fix (1.1.26080.3), and the same researcher claims a partial…

vulnerability09 Jul 20:38Zmulti-sourceOpen finding →

Earlier coverage (3)

2026-06-12HIGH"GreatXML": unpatched BitLocker bypass via crafted XML on the recovery partition, PoC public, practical severity contested"GreatXML": unpatched BitLocker bypass with public PoC, crafted XML files on the recovery partition yield a SYSTEM shell in WinRE; severity is contested (an initial Defender offline scan, which requires admin, must have run once) (SecurityWeek, 2026-06-11).2026-06-11HIGH"RoguePlanet" Microsoft Defender zero-day: TOCTOU race in the scan engine yields a SYSTEM shell, no CVE, no patchA new Microsoft Defender SYSTEM-LPE zero-day, "RoguePlanet," dropped as a public PoC hours after June Patch Tuesday, a TOCTOU race in the Defender scan engine, no CVE and no patch (BleepingComputer, 2026-06-09). No in-the-wild use reported yet; monitoring is the only mitigation.2026-05-19NOTABLEupdatedNATOA1MiniPlasma: 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 itThe researcher Chaotic Eclipse (also Nightmare Eclipse) released MiniPlasma on 2026-05-17, an exploit for the HsmOsBlockPlaceholderAccess routine of the Windows Cloud Files Mini Filter Driver (cldflt.sys), the flaw Google Project Zero reported in 2020 as CVE-2020-17103, which opened a SYSTEM command prompt from a standard user on Windows 11 with the May 2026 updates; BleepingComputer and Will Dormann reproduced it. Microsoft re-released CVE-2020-17103 on 2026-06-09 and recommends the June 2026 Windows updates to address MiniPlasma; it scores the flaw CVSS 3.1 7.0 and lists it as not exploited.

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Threats3
  • Vulns3

Source distribution

  • msrc.microsoft.com6 (29%)
  • bleepingcomputer.com4 (19%)
  • security-hub.ncsc.admin.ch2 (10%)
  • securityweek.com2 (10%)
  • theregister.com2 (10%)
  • attack.mitre.org1 (5%)
  • heise.de1 (5%)
  • microsoft.com1 (5%)
  • other2 (10%)
All cited sources (21)