Microsoft Slams Public Zero-Day Disclosures Amid GitHub Researcher Account Removal
Microsoft condemns public zero-day disclosures by researcher Chaotic Eclipse; six Windows vulnerabilities under active
Run Microsoft?
Get an email when a reviewed story names Microsoft, usually within the hour.
Free. Your list stays private and never appears in a subject line. One click stops it. How Vendor Watch worksPrivacy
Summary
Microsoft publicly criticized researcher Chaotic Eclipse for disclosing multiple unpatched zero-day vulnerabilities affecting Windows Defender, BitLocker, and other components without prior coordination. The disclosures, including CVEs for BlueHammer, RedSun, and UnDefend, have resulted in active exploitation in the wild. Following the incident, GitHub removed the researcher's account, escalating tensions between Microsoft and the security research community over coordinated vulnerability disclosure practices.
The lesson from this incident
Full lessonMicrosoft's public criticism of researcher Chaotic Eclipse reveals a breakdown in coordinated vulnerability disclosure processes, resulting in unpatched zero-day vulnerabilities being exploited in the wild. The incident demonstrates how poor vulnerability management coordination between vendors and researchers can lead to active exploitation of critical security flaws in Windows Defender, BitLocker, and other essential components. GitHub's removal of the researcher's account further escalated tensions, highlighting the need for clear disclosure policies and established communication channels. Organizations relying on affected Microsoft products face immediate security risks due to these unpatched vulnerabilities.
What helps against this
How we list vendors- Vulnerability scanning and prioritisation
You know which systems are vulnerable, and which ones to fix first.
- Automated patch management
Known holes get closed in days, not months.
- Endpoint detection and response (EDR and XDR)
Malware and hands-on-keyboard attackers on laptops and servers get spotted and stopped.
Indicators of Compromise
- cve — CVE-2026-33825
- cve — CVE-2026-41091
- cve — CVE-2026-45498
- cve — CVE-2026-45585