WINDOWS DNS · CVE-2026-105520 · Infrastructure
NO FIX YET
Windows DNS resolves a symbolic or hard link before accessing a file, so a user with some access can be tricked into reading or writing a file they should not reach. An attacker with valid credentials on the network can elevate their privileges.
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.
Organisations running Windows Server as a DNS server. The sources do not say which Windows builds are affected, and they do not give a fixed version. Hosts that do not run the DNS Server role are not exposed through this flaw.
Not affected if no-dns-server-role
Who cares self-hosted, windows, windows-dns
Get-WindowsFeature DNS in PowerShell).winver and compare it with the fixed build in Microsoft's advisory for CVE-2026-105520.No fix yet, per the sources.
Improper link resolution before file access ('link following') in Windows DNS allows an authorized attacker to elevate privileges over a network.
This page as .md · .json · CVSS:3.1/AV:N/AC:L/PR:H/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.