DESKTOP WINDOW MANAGER · CVE-2026-105528 · Infrastructure
NO FIX YET
Desktop Window Manager, the Windows component that composes application windows, has a heap-based buffer overflow. A signed-in attacker with an account on the machine can use it to 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.
Affects Windows machines where a user can sign in locally, so the risk is to shared or multi-user systems and to any attacker who already has a foothold on a machine. The sources do not list affected Windows builds or the patched update, so the exposed range is unknown. Single-user machines with only trusted accounts are lower priority but still need the vendor update once it is available.
Not affected if no-local-accounts-untrusted
Who cares desktop-window-manager, multi-user-systems, windows
winver and compare it against the Microsoft security update for CVE-2026-105528 (unknown: the sources do not list affected builds)No fix yet, per the sources.
Heap-based buffer overflow in Desktop Window 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.