CVE-2026-121673 · Infrastructure
NO FIX YET
A memory-safety bug in the Windows Filter Manager driver lets a user who already has local access corrupt memory and elevate their privileges. An attacker who can run code on the machine can gain system-level rights.
first public Nov 10, 2026 · 1 source
Could this affect your app?
Free first check from your website. Connect your repo for the full answer.
Only machines running affected Windows versions where an attacker already has a local account or code execution. The sources do not state which Windows builds are affected or which update fixes it. Servers and workstations with untrusted local users are the priority to check.
Not affected if no-local-untrusted-users
Who cares filter-manager, windows
winver or systeminfo and compare it to the fixed build in Microsoft's security update guide, which the sources do not name.No fix yet, per the sources.
Use after free in Windows Filter Manager allows an authorized attacker to elevate privileges locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Check it with your coding agent
It reads this page and tells you if your code is affected.
Are you affected?
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.