WINDOWS LINK LAYER TOPOLOGY DISCOVERY · CVE-2026-88244 · Infrastructure
NO FIX YET
A use-after-free bug in the Windows Link Layer Topology Discovery (LLTD) protocol handling lets an unauthorized attacker run code on the affected machine. The attacker must be on the same network segment (adjacent network).
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 with LLTD active on an adjacent network segment are the exposed systems; the sources do not say which Windows versions or default settings are affected. Machines on networks with no untrusted neighbors are lower risk, but the sources do not say more.
Not affected if isolated-network
Who cares adjacent-network, lltd, windows
Unknown from the sources. In the analyst’s queue.
No fix yet, per the sources.
Use after free in Windows Link Layer Topology Discovery Protocol allows an unauthorized attacker to execute code over an adjacent network.
This page as .md · .json · CVSS:3.1/AV:A/AC:H/PR:N/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.