Skip to main content

CVE-2026-122176Microsoft Windows 10 heap-based buffer overflow

Schedule itHigh8.8EPSS not scored yet

CVE-2026-122176 is a heap-based buffer overflow in Microsoft Windows 10, rated high (8.8 on CVSS 3.1).

Why this priority: High severity, with no exploitation signal yet.

Published · Updated · NVD status: Awaiting Analysis

What it is

A buffer on the heap overflows and corrupts neighbouring data structures.

How it is reached

An attacker can exploit it over the network, with an ordinary user account, and nobody has to click anything.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. 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 10. Fixed builds: Windows 10 Version 1607: 10.0.14393.9688; Windows 10 Version 1809: 10.0.17763.9487; Windows 10 Version 21H2: 10.0.19044.7846; Windows 10 Version 22H2: 10.0.19045.7846. Other affected products have their own fixed versions on this page.
  2. Until it is patched, review who holds accounts that can reach it.

Description from NVD

Heap-based buffer overflow in Windows SMB allows an authorized attacker to execute code over a network.

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

  • Authenticated network access. An account is needed, so exposure follows who can sign in: customers, partners or staff.
  • 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 10 run in your systems, and at which version?
  • Which of those instances can be reached from the internet or partner networks?
  • 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.