Skip to main content

CVE-2026-112806Microsoft Windows 10 insufficiently protected credentials

Low priorityMedium4.7EPSS not scored yet

CVE-2026-112806 is a insufficiently protected credentials in Microsoft Windows 10, rated medium (4.7 on CVSS 3.1).

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

Published · Updated · NVD status: Awaiting Analysis

What it is

Credentials are stored or sent in a way others can recover.

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. Success also depends on conditions the attacker does not fully control.

What an attacker gains

A successful attack can read the data it protects. In practice, this kind of flaw lets an attacker sign in with credentials the vendor shipped or stored unprotected.

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. Limit who can run code or sign in on the hosts that run it.

Description from NVD

Insufficiently protected credentials in Windows Print Spooler Components 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

  • Credentials kept in code, configuration, images or firmware. The flaw sits between a stored secret and anyone who can read where it is kept.

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.
  • Between a stored secret and anyone who can read where it is kept. An attacker who crosses it can sign in with credentials the vendor shipped or stored unprotected.

Questions to answer about your own systems

  • Where does Microsoft Windows 10 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.