# CVE-2022-50238: Security feature bypass in Windows

> The local Windows driver blocklist is outdated compared to the online list, allowing potentially vulnerable drivers to load unless WDAC policies are manually synchronized.

- **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-m379-7mfm-wqr6

## What is CVE-2022-50238?

CVE-2022-50238 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 on-endpoint Microsoft vulnerable driver blocklist is not fully synchronized with the online Microsoft recommended driver block rules. Some entries present on the online list have been excluded from the on-endpoint blocklist longer than the expected periodic monthly Windows updates. It is possible to fully synchronize the driver blocklist using WDAC policies. NOTE: The vendor explains that Windows Update provides a smaller, compatibility-focused driver blocklist for general users, while the full XML list is available for advanced users and organizations to customize at the risk of usability issues.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs), CWE-820 (Missing Synchronization)

## Which versions are affected by CVE-2022-50238?


## How do I fix CVE-2022-50238?

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

## Is CVE-2022-50238 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-50238 and fix it if it is affected.

What it is: CVE-2022-50238 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-2022-50238 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-2022-50238/ (Markdown: https://insights.sbomify.com/CVE-2022-50238/index.md)
```

## Sources

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

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