CVE-2026-50416: CVE-2026-50416: Exposure of sensitive information to an unauthorized actor in Windows Win32K allows an aut…
microsoft · windows 11 24h2 · NVD published 2026-07-14 · posted 2026-07-14 · last modified 2026-07-20
What it is
Exposure of sensitive information to an unauthorized actor in Windows Win32K allows an authorized attacker to disclose information locally.
| Weakness | CWE-200 |
|---|---|
| CVSS vector | CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N (source: [email protected]) |
| ATT&CK tactics | Collection |
Exploitation evidence
First exploit evidence seen: 2026-07-14 (earliest date across the sources below).
Exploited in the wild
No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).
Public exploit code
GitHub proof-of-concept repositories
2 public repositories from 2 accounts, first seen 2026-07-14. Most starred: karollooool/CVE-2026-50416-writeup-and-poc (49 stars), view repository.
Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.
Sources: nomi-sec/PoC-in-GitHub.
How to fix it
Fixed versions
- microsoft windows 11 24h2: upgrade to 10.0.26100.8875 or later
- microsoft windows 11 25h2: upgrade to 10.0.26200.8875 or later
- microsoft windows 11 26h1: upgrade to 10.0.28000.2525 or later
- microsoft windows server 2025: upgrade to 10.0.26100.33158 or later
Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.
Vendor advisories and patches
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50416 (Patch, Vendor Advisory)
MITRE ATT&CK mitigations for this chain
- M1057 Data Loss Prevention (for T1005) : Data loss prevention can restrict access to sensitive data and detect sensitive data that is unencrypted.
Detection Generic guidance
- Collection: Watch for bulk reads of databases, file shares or mailboxes by the affected service.
Response checklist Generic guidance
- Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
- Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
- Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
- Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.