CVE-2025-59033
The Microsoft vulnerable driver block list is implemented as …
The Microsoft vulnerable driver block list is implemented as Windows Defender Application Control (WDAC) policy. Entries that specify only the to-be-signed (TBS) part of the code signer certificate are properly blocked, but entries that specify the signing certificate's TBS hash along with a 'FileAttribRef' qualifier (such as file name or version) may not be blocked, whether hypervisor-protected code integrity (HVCI) is enabled or not. NOTE: The vendor disputes this CVE ID assignment and states that the driver blocklist is intended for use with HVCI.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- learn.microsoft.com/en-us/windows/security/application-security/application-control/app-co
- learn.microsoft.com/en-us/windows/security/hardware-security/enable-virtualization-based-p
- x.com/JonnyJohnson_/status/1895103112924307727
- nvd.nist.gov/vuln/detail/CVE-2025-59033
- cve.org/CVERecord?id=CVE-2025-59033
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.