CVE-2026-113753 · Infrastructure
NO FIX YET
Microsoft Windows Hyper-V mishandles a pointer taken from untrusted input, so the code dereferences memory it should not. An attacker who already has an authorized local account can raise their 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.
Only Windows machines with the Hyper-V role enabled are in scope, and the attacker must already have a local account on that machine. The sources do not give affected Windows builds. unknown
Not affected if hyper-v-not-enabled
Who cares hyper-v, windows
Unknown from the sources. In the analyst’s queue.
No fix yet, per the sources.
Untrusted pointer dereference in Windows Hyper-V allows an authorized attacker to elevate privileges locally.
This page as .md · .json · CVSS:3.1/AV:L/AC:L/PR:H/UI:N/S:C/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.