CVE-2026-83885: Windows Virtualization-Based Security (VBS) Enclave Spoofing Vulnerability
Inadequate encryption strength in Windows Virtualization-Based Security (VBS) Enclave allows an authorized attacker to perform spoofing locally.
Other sources
Windows Virtualization-Based Security (VBS) Enclave Spoofing Vulnerability
— Microsoft
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.33650Patch KB5126646 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26300.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.28000.3231Patch KB5127646 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26100.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.26200.9711Patch KB5127648 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 10.0.20348.5761Patch KB5126655
Event History
Frequently Asked Questions
What level of access does an attacker need to exploit this issue?
The attacker must already be authorized on the affected system and exploit the weakness locally. The provided CVSS vector indicates low privileges are required and no user interaction is needed.
Is this exploitable remotely?
No. The provided CVSS vector identifies local attack access, so an attacker needs local access to an affected Windows system.
What security impact is indicated?
The issue may allow spoofing and has an integrity impact, while the provided vector indicates no confidentiality or availability impact. Its scope is marked changed, meaning the impact can extend beyond the initially vulnerable security authority.
Which products are identified as affected?
The listed affected products are Microsoft Windows 11, Microsoft Windows Server 2022, and Microsoft Windows Server 2025.