CVE-2026-105562: Windows data leak in Container Manager

Summary

Time-of-check time-of-use (toctou) race condition in Windows Container Manager Service allows an authorized attacker to disclose information locally.

cve.now Index

5Pcve.now Index 5 of 100 · methodology v3 · provisional

Exploitation0/40No signal
Exposure?/25Unknown. No advisory context yet
Reach?/20Unknown. No tracked technology or package matched
Severity4.7/10CVSS 4.7
No patch0/5No signal

What would change the score

Would score about 60 if added to CISA KEV
Would score about 55 if CISA's SSVC rates exploitation active
Would score about 27 if advisories confirm default setups are exposed

How the score works · Rankings

What to do

Upgrade to a fixed version: 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, or one of 2 more.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-105562 (Windows Container Manager Service Information Disclosure Vulnerability), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-105562 (entry last updated 2026-11-10):
Affected:
- Microsoft Windows 10 Version 21H2: from 10.0.19044.0, fixed in 10.0.19044.7846
- Microsoft Windows 10 Version 22H2: from 10.0.19045.0, fixed in 10.0.19045.7846
- Microsoft Windows 11 version 23H2: from 10.0.22631.0, fixed in 10.0.22631.7711
- Microsoft Windows 11 Version 23H2: from 10.0.22631.0, fixed in 10.0.22631.7711
- Microsoft Windows 11 Version 24H2: from 10.0.26100.0, fixed in 10.0.26100.9974
- Microsoft Windows 11 Version 25H2: from 10.0.26200.0, fixed in 10.0.26200.9974
- Microsoft Windows 11 version 26H1: from 10.0.28000.0, fixed in 10.0.28000.3501
- Microsoft Windows 11 Version 26H2: from 10.0.26300.0, fixed in 10.0.26300.9974
Fixed versions: 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, 10.0.28000.3501, 10.0.26300.9974.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-105562 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-105562 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-105562
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Entry: https://cve.now/CVE-2026-105562
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example get_vulnerability with id CVE-2026-105562.

Timeline

Nov 10, 2026, 6:19 PM UTCCVE published
Nov 10, 2026, 6:30 PM UTCFirst seen by cve.now
Nov 10, 2026, 9:03 PM UTCCISA SSVC assessment
Exploitation: none · Automatable: no · Technical impact: partial
Nov 10, 2026, 11:50 PM UTCRecord last updated

Affected versions

Microsoft Windows 10 Version 21H2
From 10.0.19044.0 · fixed in 10.0.19044.7846
Microsoft Windows 10 Version 22H2
From 10.0.19045.0 · fixed in 10.0.19045.7846
Microsoft Windows 11 version 23H2
From 10.0.22631.0 · fixed in 10.0.22631.7711
Microsoft Windows 11 Version 23H2
From 10.0.22631.0 · fixed in 10.0.22631.7711
Microsoft Windows 11 Version 24H2
From 10.0.26100.0 · fixed in 10.0.26100.9974
Microsoft Windows 11 Version 25H2
From 10.0.26200.0 · fixed in 10.0.26200.9974
Microsoft Windows 11 version 26H1
From 10.0.28000.0 · fixed in 10.0.28000.3501
Microsoft Windows 11 Version 26H2
From 10.0.26300.0 · fixed in 10.0.26300.9974

Evidence 3

Vendor advisory · 1

Establishes: Affected and fixed versions.

Patch
msrc.microsoft.com · update-guide/vulnerability/CVE-2026-105562

CVE record · 2

Establishes: The identifier and description.

Record
CVE List · CVE-2026-105562
Record
NVD · CVE-2026-105562

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-105562

Is CVE-2026-105562 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

Which versions are affected by CVE-2026-105562?

Windows 10 Version 21H2: from 10.0.19044.0 before 10.0.19044.7846. Windows 10 Version 22H2: from 10.0.19045.0 before 10.0.19045.7846. Windows 11 version 23H2: from 10.0.22631.0 before 10.0.22631.7711. Windows 11 Version 23H2: from 10.0.22631.0 before 10.0.22631.7711. Windows 11 Version 24H2: from 10.0.26100.0 before 10.0.26100.9974. 3 more packages are listed on the page.Source: cve.now feed data

How do I fix CVE-2026-105562?

Upgrade to a fixed version: 10.0.19044.7846, 10.0.19045.7846, 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, or one of 2 more.Source: cve.now feed data

Windows Container Manager Service Information Disclosure Vulnerability