CVE Tools

CVE-2026-65788

Desktop Window Manager Elevation of Privilege Vulnerability

No known exploitation. EPSS puts it in the 16th percentile. A vendor fix is available.

Published Updated Sources: CVE.org, NVD

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record
  1. Check whether your Windows version/build matches any affected Windows 11 or Windows Server 2025 builds on your devices.
  2. Install the Microsoft fix for CVE-2026-65788 using Windows Update or the Microsoft Update Guide, ensuring you reach one of the fixed build numbers listed by Microsoft.
  3. Reboot your devices after installing the updates and verify the updated build is in place.
  4. If you can’t update right away, isolate affected machines (limit who can log in and access them) until the patch is applied.

What it is

From the CVE record

Use after free in Desktop Window Manager allows an authorized attacker to elevate privileges locally.

In plain language

Written by AI from the record

This Windows local security flaw lets someone who already has some access on your PC possibly gain higher privileges; if you run Windows 11 or Windows Server 2025, you should update because this is serious and a patch is available.

CVE-2026-65788 is a local elevation of privilege issue in Windows Desktop Window Manager that can be triggered via a use-after-free memory-handling weakness, allowing an authorized attacker to elevate privileges; patches are available for affected builds of Windows 11 and Windows Server 2025.

If you're affected

  • Full account privilege escalation
  • Wider system control
  • Possible disruption from takeover
  • Increased malware impact risk

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS16th
CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.3% chance of exploitation activity in the next 30 days, which ranks it in the 16th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 3 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. OpenVAS check added
  3. Record updatedrecord updated
  4. Publishedweakness classified, att&ck mapped, record updated

Affected products

Technical detail

CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H

Scored 7.0 by NVD.

How it is reached

  • Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
  • Attack Complexity HighRequires specific conditions like a race condition or non-default configuration
  • Privileges Required LowRequires basic user-level privileges
  • User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

  • Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

  • Confidentiality HighTotal information disclosure — all data in the component is compromised
  • Integrity HighTotal loss of integrity — attacker can modify any data in the component
  • Availability HighTotal denial of service — the component is completely unavailable

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for Windows 11 Version 23H2, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store