CVE-2025-59033: Microsoft Windows · Unprotected Alternate Channel
Affects Microsoft WindowsSource CVE Database V5
Not known to be exploited · CVSS 7.4 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Sep 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Microsoft Windows | Affected
| Fixed in– |
AI-suggested
European organizations should implement the following specific mitigations: 1) Review and audit WDAC policies to identify any entries using the signing certificate's TBS hash combined with 'FileAttribRef' qualifiers, and remove or modify these entries to rely solely on the TBS part of the certificate. 2) Enforce strict code signing policies that avoid qualifiers that may cause bypasses. 3) Enable and maintain HVCI and ensure it is properly configured and updated, as it provides an additional layer of protection despite the vulnerability. 4) Monitor system logs and WDAC enforcement events for anomalies indicating potential driver loading bypass attempts. 5) Employ endpoint detection and response (EDR) solutions capable of detecting suspicious driver loads or kernel-level anomalies. 6) Stay updated with Microsoft advisories and apply patches promptly once available. 7) Conduct penetration testing and red team exercises simulating driver blocklist bypass to validate defenses. 8) Limit administrative privileges and restrict driver installation rights to reduce attack surface. These steps go beyond generic advice by focusing on WDAC policy hygiene and proactive detection tailored to this vulnerability's specifics.
Description
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.
References
- learn.microsoft.com/en-us/windows/security/application-security/application-control/app-control-for-business/design/microsoft-recommended-driver-block-rules (opens in a new tab)
- learn.microsoft.com/en-us/windows/security/hardware-security/enable-virtualization-based-protection-of-code-integrity (opens in a new tab)
- x.com/JonnyJohnson_/status/1895103112924307727 (opens in a new tab)