Driver blocklist bypass via qualified signer rules
Published Sep 8, 2025 · Updated Nov 17, 2025
Protection bypass in Microsoft Windows 10 through Server 2025 allows attackers to load drivers that qualified blocklist rules should deny. A WDAC rule combining a signer's TBS certificate hash with FileAttribRef qualifiers fails to block the matching signed driver. Exploitation requires a local driver-loading path; Microsoft disputes the CVE and states that the blocklist is intended for HVCI use.
Summary
What happened
Protection bypass in Microsoft Windows 10 through Server 2025 allows attackers to load drivers that qualified blocklist rules should deny. A WDAC rule combining a signer's TBS certificate hash with FileAttribRef qualifiers fails to block the matching signed driver. Exploitation requires a local driver-loading path; Microsoft disputes the CVE and states that the blocklist is intended for HVCI use.
The record
- CVE
- CVE-2025-59033
- Published
- Sep 8, 2025
- Updated
- Nov 17, 2025
- Vendor
- Microsoft
- Product
- Windows
- Classifications
- CWE-693, CWE-420, T1562.001
- Attack vector
- local
- Privileges
- Unavailable
Timeline
How it unfolded
- Sep 8, 2025CVE publishedPublication date reported by the CVE source.
- Nov 17, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=10 <=Server 2025
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo