Microsoft’s June 2026 Patch Tuesday is its largest monthly release yet, with about 200 vulnerabilities fixed. Thirty-three are rated critical, mostly remote code execution bugs. Six zero-days are included: one exploited in attacks and five publicly disclosed before a fix was available.
Actively exploited
CVE-2026-42897 – Exchange Server spoofing. Attackers are exploiting a flaw that lets them run JavaScript in a victim’s browser through Outlook Web Access. Microsoft had already pushed mitigations through the Exchange Emergency Mitigation Service. The Exchange team advises customers to keep those mitigations in place while the full fix rolls out.
Publicly disclosed zero-days
CVE-2026-45586– Windows CTFMON elevation of privilege to SYSTEM. It is believed to be the bug behind the leaked “GreenPlasma” exploit.CVE-2020-17103– Cloud Files Mini Filter Driver privilege escalation (“Mini-Plasma”). It was first reported in 2020 but was still exploitable.CVE-2026-45585andCVE-2026-50507– BitLocker security feature bypasses, including the “YellowKey” technique that reaches encrypted drives through WinRE. Both require physical access.CVE-2026-49160– HTTP.sys “HTTP/2 Bomb” denial of service. A newMaxHeadersCountregistry setting is available as a mitigation.
Other critical fixes
The release includes remote code execution fixes in Active Directory Domain Services (CVE-2026-45648), the Kerberos KDC (CVE-2026-47288), HTTP.sys (CVE-2026-47291), the DHCP Client (CVE-2026-44815), the Windows kernel TCP/IP stack (CVE-2026-45657, described as wormable), Hyper-V, the Remote Desktop Client and several Office components.
Within hours of the release, the same researcher behind the earlier Defender leaks published another unpatched Defender privilege escalation exploit, dubbed “RoguePlanet”.
Recommendations
- Patch Exchange servers first and confirm that EEMS mitigations stay active. Review OWA logs for suspicious script injection.
- Patch domain controllers and KDCs next (
CVE-2026-45648,CVE-2026-47288), then internet-facing IIS/HTTP.sys hosts. - After the BitLocker fix, test on a pilot group. A BitLocker key-related error may be fixed by running
reagentc /disablethenreagentc /enable. - Make sure DHCP Client and TCP/IP fixes reach all endpoints and servers, including VDI images.
- Watch for RoguePlanet-style Defender abuse until Microsoft releases a fix.