# CVE-2025-59033: Security feature bypass in Windows

> Attackers may bypass Windows Defender Application Control driver blocklists by exploiting specific certificate qualifier handling, allowing execution of blocked drivers.

- **Severity:** High 7.4 (`CVSS:3.1/AV:L/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 8 Sep 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-h935-vxwx-xh2m

## What is CVE-2025-59033?

CVE-2025-59033 is a high-severity vulnerability in Microsoft Windows, published on 8 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official 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.

Weakness: CWE-693 (Protection Mechanism Failure), CWE-420 (Unprotected Alternate Channel)

## Which versions are affected by CVE-2025-59033?


## How do I fix CVE-2025-59033?

No fix has been published for CVE-2025-59033 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-59033 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59033 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59033 and fix it if it is affected.

What it is: CVE-2025-59033 is a high-severity vulnerability in Microsoft Windows, published on 8 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59033 exists.

Affected product: Microsoft Windows. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-59033/ (Markdown: https://insights.sbomify.com/CVE-2025-59033/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-59033
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-59033
- OSV: https://osv.dev/vulnerability/CVE-2025-59033

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-59033/
Summaries are generated and may contain mistakes; the official description above is the record.