CVE-2026-62702 is a medium severity (CVSS 6.8) null pointer dereference in the Windows Graphics Kernel. An unauthenticated remote attacker could cause a denial of service on an affected Windows system. Microsoft's update guide entry lists the fix for each build, so patch through your normal process.
What's affected
The record lists Windows 10 21H2 and 22H2 and Windows 11 23H2 among the affected products (the list in the record continues; check the Microsoft entry for the full set). The weakness is CWE-476 (NULL pointer dereference).
The vector is network based with high attack complexity, no privileges and no user interaction. The scope is changed, and the only impact is on availability, which is rated high. There is no confidentiality or integrity effect in the record.
The record gives no fixed build number. Microsoft's update guide entry is the place to find the KB article that matches your Windows version.
How to check if you're exposed
Check the installed updates on each machine and compare them with the KB for the CVE.
Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5
(Get-ComputerInfo).OsBuildNumber
Focus on systems where an unexpected crash would be costly, such as shared workstations, virtual desktop hosts and servers that run a desktop experience. A kernel level fault usually shows up as a stop error and restart, so crash dump records in the event log are the first clue.
Whatever the product, a current inventory of what you run is what turns a CVE notice into a quick answer. The Gold page for this CVE tracks how its record changes over time, and the free in-browser dependency scan at gold.safeguard.sh/scan covers the application libraries you ship.
What to do now
- Read the Microsoft update guide entry and note the KB per Windows version.
- Roll out the update through your normal rings, with virtual desktop hosts and shared systems early.
- Check the event log for unexplained bugchecks on unpatched machines.
- Keep a record of systems that cannot take the update yet and who owns them.
- Make sure your endpoint tool reports patch level, so you can answer in minutes next time.
Why it matters
A null pointer dereference happens when code uses a pointer that points to nothing. In user programs the result is a crashed process. In a kernel component the result is usually a system crash, which is why the record rates availability impact high.
This is not a data theft bug. Its weight comes from where it runs: the graphics kernel sits below many applications, so a crash takes everything down. The class is CWE-476. The record does not list it as exploited in the wild.
Quick check
Will this let an attacker read my files?
Not according to the record. The vector shows no confidentiality or integrity impact. The effect is denial of service.
Sources
Last reviewed: 18 October 2026.
