KB5082052: Windows Server Security Update (April 2026)
Microsoft Windows Shell contains a protection mechanism failure vulnerability that allows an unauthorized attacker to perform spoofing over a network.
A remote attacker, without authentication, can achieve partial data exposure. Federal agencies are required to remediate by 2026-05-12 under CISA BOD 22-01.
This is a Software Vulnerability (CWE-693) (CWE-693) vulnerability in Microsoft Windows. Protection mechanism failure in Windows Shell allows an unauthorized attacker to perform spoofing over a network. Exploitation requires remote network access, low attack complexity, no authentication required, and user interaction required.
📧
Phishing link
🖼
Malicious file
🔓
Server compromised
Probably yes if any of these apply:
CISA added this CVE to the Known Exploited Vulnerabilities catalog on 2026-04-28 based on evidence of active exploitation in the wild. Federal agencies required to remediate by 2026-05-12.
Manual download
For air-gapped servers or out-of-band deployment. Microsoft Update Catalog returns every OS-version variant of this update.
↗ Microsoft Update CatalogKB5082052Manual remediation steps
Apply the Microsoft Security Update
Microsoft has released an official security update that fixes this vulnerability.
Required KB Updates
Supersedes: KB5078734, KB5078740, KB5078752, KB5078766, KB5078774, KB5078775, KB5078883, KB5078885, KB5078938, KB5079466, KB5079473
Affected Products
Fixed Build Numbers
Installation Methods
Windows Update (recommended)
Microsoft Update Catalog (manual download)
.msu installer with administrator privilegesWSUS / SCCM / Intune
Approve KB5082052 for the affected products in your update management console.
Microsoft Download Center Links
Verification
Confirm the update is installed:
Get-HotFix | Where-Object { $_.HotFixID -in @('KB5082052','KB5082060','KB5082063','KB5082123','KB5082126','KB5082127','KB5082142','KB5082198','KB5082200','KB5083768','KB5083769') }
References
Discovery Credit
Maor Dahan with Akamai
No tested PowerShell script for this entry yet. We’re prioritising automation based on user demand.