Metrics
Affected Vendors & Products
Source | ID | Title |
---|---|---|
![]() |
EUVD-2025-27143 | The Microsoft vulnerable driver block list is implemented as Windows Defender Application Control (WDAC) policy. On systems that do not have hypervisor-protected code integrity (HVCI) enabled, 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) will not be blocked. This vulnerability affects any Windows system that does not have HVCI enabled or supported (HVCI is available in Windows 10, Windows 11, and Windows Server 2016 and later). NOTE: The vendor states that the driver blocklist is intended for use with HVCI, while systems without HVCI should use App Control, and any custom blocklist entries require a granular approach for proper enforcement. |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Fri, 17 Oct 2025 19:00:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-420 | |
Metrics |
cvssV3_1
|
cvssV3_1
|
Tue, 09 Sep 2025 21:45:00 +0000
Type | Values Removed | Values Added |
---|---|---|
First Time appeared |
Microsoft
Microsoft windows Microsoft windows 10 Microsoft windows 11 Microsoft windows Server 2016 Microsoft windows Server 2019 Microsoft windows Server 2022 Microsoft windows Server 2025 |
|
Vendors & Products |
Microsoft
Microsoft windows Microsoft windows 10 Microsoft windows 11 Microsoft windows Server 2016 Microsoft windows Server 2019 Microsoft windows Server 2022 Microsoft windows Server 2025 |
Mon, 08 Sep 2025 18:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Weaknesses | CWE-693 | |
Metrics |
cvssV3_1
|
Mon, 08 Sep 2025 15:15:00 +0000
Type | Values Removed | Values Added |
---|---|---|
Description | The Microsoft vulnerable driver block list is implemented as Windows Defender Application Control (WDAC) policy. On systems that do not have hypervisor-protected code integrity (HVCI) enabled, 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) will not be blocked. This vulnerability affects any Windows system that does not have HVCI enabled or supported (HVCI is available in Windows 10, Windows 11, and Windows Server 2016 and later). NOTE: The vendor states that the driver blocklist is intended for use with HVCI, while systems without HVCI should use App Control, and any custom blocklist entries require a granular approach for proper enforcement. | |
References |
|
|

Status: PUBLISHED
Assigner: mitre
Published:
Updated: 2025-10-17T18:46:39.089Z
Reserved: 2025-09-08T00:00:00.000Z
Link: CVE-2025-59033

Updated: 2025-09-08T17:36:20.306Z

Status : Awaiting Analysis
Published: 2025-09-08T15:15:37.983
Modified: 2025-10-17T19:15:37.940
Link: CVE-2025-59033

No data.

Updated: 2025-09-09T21:32:03Z