Microsoft has come out strongly in favor of Coordinated Vulnerability Disclosure (CVD), urging the research community to share their findings and give affected vendors an opportunity to better understand the impact and address them before they are publicly disclosed.  The development comes after a researcher named Chaotic Eclipse (aka Nightmare-Eclipse) disclosed details of multiple zero-day vulnerabilities affecting multiple **Windows** components, including **Defender** and **BitLocker**, over the past month, citing a breakdown in **Microsoft's** handling of the vulnerability disclosure process. "In recent weeks, several zero-day vulnerabilities have been publicly disclosed," the tech giant [said](https://www.microsoft.com/en-us/msrc/blog/2026/05/a-shared-responsibility-protecting-customers-through-coordinated-vulnerability-disclosure). "The details of these vulnerabilities were not shared with **Microsoft** prior to release, and the disclosures put our customers at unnecessary risk." "In response to the unnecessary risk created by these disclosures, our security teams have been working around the clock to understand the impact, protect our customers, and develop security updates." ### Vulnerabilities Disclosed The vulnerabilities include **BlueHammer** (**CVE-2026-33825**), **RedSun** (**CVE-2026-41091**), **UnDefend** (**CVE-2026-45498**), **YellowKey** (**CVE-2026-45585**), **GreenPlasma**, and **MiniPlasma**. Following disclosure, BlueHammer, RedSun, and UnDefend have all come under active exploitation in the wild. **Microsoft** said it "firmly" opposes such uncoordinated disclosures and that putting proof-of-concept code for unpatched vulnerabilities can have "real-world consequences" when they end up in the hands of bad actors. ### Microsoft's Response "We invite diverse perspectives that help the security community work together to protect everyone. We realize that we will not always agree on everything, but we are committed to transparency and continue to create opportunities for dialogue," the tech giant added. "These conversations happen at researcher appreciation events, security conferences, and the everyday work we do together to understand and address vulnerabilities." ### Fallout and Repercussions The fallout from these disclosures is said to have led **GitHub** to takedown the researcher's account last week. Although the exploit code for the six vulnerabilities was subsequently uploaded to **GitLab**, the [newly created account](https://gitlab.com/nightmare-eclipse) has since been blocked. "So let me get this straight, when I actively asked you to communicate with me, you refused, humiliated me, and made sure to insult me in front of people," the researcher [said](https://deadeclipse666.blogspot.com/2026/05/july-14th.html) in a post published over the weekend. "You defame me in public with your **CVE-2026-45585** advisory even though you literally deleted the **Microsoft** account I used to report bugs to you with and I got zero pennies from doing so and I still happily did like an idiot. Now you take the courtesy to flag my **GitHub** account and wipe it out of the public, just like that? You are proving to everyone that you [sic] actively escalating this conflict but I'm done begging you." The researcher also said they intend to release something on July 14, 2026, that "will make sure your bones are shattered that day."