Skip to main content

CVE-2026-95946Microsoft Windows 11 out-of-bounds read

Low priorityMedium5.5EPSS not scored yet

CVE-2026-95946 is a out-of-bounds read in Microsoft Windows 11, rated medium (5.5 on CVSS 3.1).

Why this priority: Medium severity, with no exploitation signal.

Published · Updated · NVD status: Awaiting Analysis

What it is

Code reads past the end of a buffer, leaking memory contents or crashing.

How it is reached

An attacker can exploit it by someone who can already run code or sign in on the machine, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker crash the process, read memory, or in the worst case run code.

Is it being exploited?

There is no public report of exploitation yet.

What to do

  1. Apply the update for your edition of Microsoft Windows 11. Fixed builds: Windows 11 Version 23H2: 10.0.22631.7711; Windows 11 Version 24H2: 10.0.26100.9974; Windows 11 Version 25H2: 10.0.26200.9974; Windows 11 version 26H1: 10.0.28000.3501; Windows 11 Version 26H2: 10.0.26300.9974. Other affected products have their own fixed versions on this page.
  2. Limit who can run code or sign in on the hosts that run it.

Description from NVD

Out-of-bounds read in Windows Graphics Kernel allows an authorized attacker to disclose information locally.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

  • Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
  • Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.

Trust boundaries in play

  • Host boundary. The attacker needs a foothold on the machine first; the flaw turns a small foothold into a bigger one.
  • Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.

Questions to answer about your own systems

  • Where does Microsoft Windows 11 run in your systems, and at which version?
  • Which of those hosts also run code or users you do not fully trust?
  • What can it reach once compromised: which data stores, secrets and services?

Sources

  • CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
  • Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
  • Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
  • Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.