Windows Performance Counters Remote Code Execution Vulnerability

Check whether my systems are affected by CVE-2026-95975 (Windows Performance Counters Remote Code Execution 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-95975 (entry last updated 2026-11-10):
Affected:
- Microsoft Windows 10 Version 1607: from 10.0.14393.0, fixed in 10.0.14393.9688
- Microsoft Windows 10 Version 1809: from 10.0.17763.0, fixed in 10.0.17763.9487
- 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
- and 7 more affected products, listed on https://cve.now/CVE-2026-95975
Fixed versions: 10.0.14393.9688, 10.0.17763.9487, 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, 10.0.20348.5870, 10.0.26100.33822.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-95975 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-95975 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-95975
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.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-95975
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-95975.