CVE-2026-96994 · Infrastructure
NO FIX YET
A use-after-free bug in the Windows Winsock networking component lets an authorized local user trigger memory corruption. An attacker with a low-privilege account can use it to elevate privileges on the machine.
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.
Windows machines where a user already has a local account can be elevated to higher privileges through this flaw. The sources do not name affected Windows builds or whether a patch is available, so unknown. Systems where only trusted administrators log in are less exposed.
Not affected if no-local-accounts
Who cares windows, winsock
Unknown from the sources.
No fix yet, per the sources.
Use after free in Winsock allows an authorized attacker to elevate privileges locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:H/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.