Researcher Drops Two Unpatched Windows Zero-Day Exploits, "YellowKey" & "GreenPlasma"

Researcher Drops Two Windows Zero-Days, 'YellowKey' and 'GreenPlasma,' Exposing BitLocker and Escalating Privileges

CRITICAL
May 15, 2026
May 18, 2026
m read
VulnerabilityCyberattack

Related Entities(initial)

Organizations

MicrosoftMicrosoft Security Response Center (MSRC)

Products & Tech

BitLockerWindows 11Windows Server 2022Windows Server 2025

Other

Chaotic EclipseGreenPlasmaNightmare EclipseYellowKey

Full Report(when first published)

Executive Summary

A security researcher, using the alias Chaotic Eclipse, has publicly disclosed two unpatched zero-day vulnerabilities in Microsoft Windows, releasing proof-of-concept (PoC) exploit code for both. The disclosure was made in an act of protest against the Microsoft Security Response Center (MSRC) bug reporting process. The first vulnerability, dubbed YellowKey, allows an attacker with physical access to bypass BitLocker encryption on modern Windows versions. The second, GreenPlasma, is a local privilege escalation (LPE) flaw in the Windows Collaborative Translation Framework. The public availability of these exploits creates a critical situation for Windows administrators, as there are no official patches, and reports indicate the exploits are already being weaponized.


Vulnerability Details

YellowKey: BitLocker Encryption Bypass

  • Description: A critical vulnerability that allows an attacker with physical access to a device to bypass BitLocker full-disk encryption. It affects Windows 11, Windows Server 2022, and Windows Server 2025.
  • Attack Vector: The exploit leverages the Windows Recovery Environment (WinRE). An attacker places specially crafted FsTx files onto a USB drive or the system's EFI partition. By rebooting the machine into WinRE, a command shell is triggered, providing access to the unlocked, decrypted BitLocker-protected volume.
  • Impact: Complete loss of data confidentiality on stolen or physically accessed devices, even those protected by BitLocker. The researcher claims it works even with TPM+PIN, though this is debated, with others only confirming it on TPM-only systems. This is a form of T1553 - Subvert Trust Controls.

GreenPlasma: Local Privilege Escalation

  • Description: An LPE vulnerability in the Windows Collaborative Translation Framework service (CTFMON).
  • Attack Vector: The PoC demonstrates how a low-privileged user can create arbitrary memory-section objects. This can be abused to manipulate privileged services that interact with the CTFMON service, ultimately allowing the attacker to execute code with SYSTEM-level privileges.
  • Impact: A local attacker or malware that has gained initial low-privileged access can use this exploit to gain full control over the system, allowing them to disable security software, steal credentials, and deploy ransomware. This is a classic T1068 - Exploitation for Privilege Escalation.

Exploitation Status

Both vulnerabilities are considered zero-days with publicly available PoC exploit code. This significantly lowers the bar for other threat actors to adopt and weaponize them. Reports from security news outlets suggest that the exploits were already being integrated into active attack campaigns within 24 hours of their public release.


Impact Assessment

The public disclosure of unpatched, working exploits for critical vulnerabilities presents a severe risk to all organizations using modern Windows operating systems.

  • YellowKey undermines the trust in BitLocker, a foundational security feature for protecting data at rest. This is particularly dangerous for laptops and mobile devices that are at risk of being lost or stolen.
  • GreenPlasma provides a reliable pathway for attackers to escalate privileges. Most advanced cyberattacks rely on LPE to move from an initial foothold (e.g., a compromised user account) to full domain compromise.

The combination of these two flaws being available simultaneously creates a potent cocktail for attackers.


Cyber Observables — Hunting Hints

The following patterns may help identify vulnerable or compromised systems:

  • For YellowKey:

    • Physical Security Logs: Any instance of unauthorized physical access to a server or laptop should be treated as a potential compromise.
    • Boot Logs: Monitor for unexpected reboots into the Windows Recovery Environment (WinRE). This is highly anomalous for server systems.
    • File System: Look for the presence of unusual FsTx files on EFI partitions or removable media connected to sensitive systems.
  • For GreenPlasma:

    • Process Monitoring: Monitor for anomalous behavior or unexpected child processes originating from the ctfmon.exe process.
    • Memory Analysis: Advanced memory forensics may be able to detect the creation of malicious memory-section objects, though this is difficult to perform at scale.

Detection Methods

  • EDR/Behavioral Analysis: Configure EDR solutions to alert on suspicious process chains involving ctfmon.exe or any attempts by low-privilege processes to interact with system-level services in an unusual manner.
  • WinRE Monitoring: While difficult, it may be possible to monitor for changes to the WinRE configuration (ReAgentc.xml) or for logs indicating the system has booted into recovery mode.

Remediation Steps

As of this report, there are no official patches from Microsoft. The following are compensating controls:

  • For YellowKey:

    1. Physical Security: Enforce strict physical security controls for all sensitive systems, especially servers in data centers. This is the primary mitigation.
    2. BitLocker Pre-boot Authentication: While the researcher claims TPM+PIN is not a full mitigation, it adds a significant barrier. Enforce the use of a PIN or startup key for BitLocker on all endpoints. This prevents the system from booting to WinRE without user authentication.
  • For GreenPlasma:

    1. Application Control: Use application allowlisting (e.g., AppLocker, WDAC) to prevent unprivileged users from running unauthorized code, which is the first step before an LPE exploit can be used.
    2. Principle of Least Privilege: Ensure users do not have local administrator rights. This won't stop the LPE exploit itself, but it limits the damage an attacker can do before attempting to escalate.
    3. Monitor for Updates: Be prepared to deploy Microsoft's security update for these vulnerabilities on an emergency basis as soon as it is released.

Timeline of Events

1
May 14, 2026
Researcher 'Chaotic Eclipse' publicly discloses the YellowKey and GreenPlasma vulnerabilities and their PoC exploits.
2
May 15, 2026
This article was published

Article Updates

May 16, 2026

New context for YellowKey/GreenPlasma zero-days: released post-Patch Tuesday, affects Server 2026, and researcher's history of prior exploits.

The new article provides additional context regarding the YellowKey and GreenPlasma zero-day exploits. It highlights that the PoCs were released immediately after Microsoft's May Patch Tuesday, emphasizing the lack of official patches. The affected server versions for GreenPlasma are updated to include Windows Server 2026. Crucially, the article references the researcher's past disclosure of 'BlueHammer,' which was subsequently exploited, reinforcing the high likelihood of these new exploits being weaponized by threat actors.

May 17, 2026

New hunting hints and refined technical analysis for YellowKey and GreenPlasma zero-days, including clarification on TPM bypass for BitLocker.

This update provides more specific hunting hints for the GreenPlasma privilege escalation vulnerability, including monitoring for Windows Security Event ID 4673 and suspicious cmd.exe or powershell.exe processes spawning with SYSTEM privileges, often preceded by whoami /priv commands. For YellowKey, the analysis clarifies that the BitLocker bypass is reported to work even when a Trusted Platform Module (TPM) is in use, undermining TPM-based key protection. Mitigation strategies are further detailed with references to D3FEND techniques like Physical Security and Executable Allowlisting.

May 18, 2026

New details for YellowKey BitLocker bypass confirm Windows 10 is unaffected, specify CTRL key trigger in WinRE, and add enhanced mitigations like BIOS/UEFI passwords.

Further analysis of the YellowKey BitLocker bypass reveals that Windows 10 is not affected, clarifying the scope of the vulnerability. The attack specifically involves holding the CTRL key during the Windows Recovery Environment (WinRE) boot process to trigger the flaw, as reproduced by researcher Will Dormann. There is also speculation regarding the possibility of an intentional backdoor. Additional mitigation strategies now include setting strong BIOS/UEFI passwords and considering file-level encryption for sensitive data, beyond just BitLocker with a PIN.

Timeline of Events

1
May 14, 2026

Researcher 'Chaotic Eclipse' publicly discloses the YellowKey and GreenPlasma vulnerabilities and their PoC exploits.

Article Author

Jason Gomes

Jason Gomes

• Cybersecurity Practitioner

Cybersecurity professional with over 10 years of specialized experience in security operations, threat intelligence, incident response, and security automation. Expertise spans SOAR/XSOAR orchestration, threat intelligence platforms, SIEM/UEBA analytics, and building cyber fusion centers. Background includes technical enablement, solution architecture for enterprise and government clients, and implementing security automation workflows across IR, TIP, and SOC use cases.

Threat Intelligence & AnalysisSecurity Orchestration (SOAR/XSOAR)Incident Response & Digital ForensicsSecurity Operations Center (SOC)SIEM & Security AnalyticsCyber Fusion & Threat SharingSecurity Automation & IntegrationManaged Detection & Response (MDR)

Tags

BitLockerExploitGreenPlasmaMicrosoftPrivilege EscalationWindowsYellowKeyZero-Day

📢 Share This Article

Help others stay informed about cybersecurity threats

🎯 MITRE ATT&CK Mapped

Every tactic, technique, and sub-technique used in this threat has been identified and mapped to the MITRE ATT&CK framework for consistent, actionable threat language.

🧠 Enriched & Analyzed

Observables and indicators of compromise (IOCs) have been extracted and cataloged. Risk has been assessed and correlated with known threat actors and historical campaigns.

🛡️ Actionable Guidance

Detection rules, incident response steps, and D3FEND-aligned mitigation strategies are included so your team can act on this intelligence immediately.

🔗 STIX Visualizer

Structured threat data is packaged as a STIX 2.1 bundle and can be visualized as an interactive graph — relationships between actors, malware, techniques, and indicators.

Sigma Generator

Sigma detection rules are derived from the threat techniques in this article and can be converted for deployment across any major SIEM or EDR platform.