Every applicability statement published about this vulnerability, kept as each source wrote it rather than merged into one verdict. Where sources disagree, both positions are shown.
A statement that names no version covers the whole product, which is not the same as your version falling inside a range. Orderings marked best effort come from schemes with no published comparison algorithm; exact ones follow a published specification.
Precedence decides which claim wins when two sources describe the same product over the same version range. It is a property of the source, not of the claim, and changing it re-ranks the data without re-reading a single document.
| Product | Status | Versions | Remediation | Source | |
|---|---|---|---|---|---|
| Microsoft/Windows 10 Version 1607 Microsoft · Windows 10 Version 1607 | affected | >= 10.0.14393.0, < 10.0.14393.9339 | none available | cve_cna | |
| Microsoft/Windows 10 Version 1809 Microsoft · Windows 10 Version 1809 | affected | >= 10.0.17763.0, < 10.0.17763.9020 | none available | cve_cna | |
| Microsoft/Windows 10 Version 21H2 Microsoft · Windows 10 Version 21H2 | affected | >= 10.0.19044.0, < 10.0.19044.7548 | none available | cve_cna | |
| Microsoft/Windows 10 Version 22H2 Microsoft · Windows 10 Version 22H2 | affected | >= 10.0.19045.0, < 10.0.19045.7548 | none available | cve_cna | |
| Microsoft/Windows 11 version 23H2 Microsoft · Windows 11 version 23H2 | affected | >= 10.0.22631.0, < 10.0.22631.7376 | none available | cve_cna | |
| Microsoft/Windows 11 Version 23H2 Microsoft · Windows 11 Version 23H2 | affected | >= 10.0.22631.0, < 10.0.22631.7376 | none available | cve_cna | |
| Microsoft/Windows 11 Version 24H2 Microsoft · Windows 11 Version 24H2 | affected | >= 10.0.26100.0, < 10.0.26100.8875 | none available | cve_cna | |
| Microsoft/Windows 11 Version 25H2 Microsoft · Windows 11 Version 25H2 | affected | >= 10.0.26200.0, < 10.0.26200.8875 | none available | cve_cna | |
| Microsoft/Windows 11 version 26H1 Microsoft · Windows 11 version 26H1 | affected | >= 10.0.28000.0, < 10.0.28000.2525 | none available | cve_cna | |
| Microsoft/Windows Server 2012 Microsoft · Windows Server 2012 | affected | >= 6.2.9200.0, < 6.2.9200.26226 | none available | cve_cna | |
| Microsoft/Windows Server 2012 (Server Core installation) Microsoft · Windows Server 2012 (Server Core installation) | affected | >= 6.2.9200.0, < 6.2.9200.26226 | none available | cve_cna | |
| Microsoft/Windows Server 2012 R2 Microsoft · Windows Server 2012 R2 | affected | >= 6.3.9600.0, < 6.3.9600.23291 | none available | cve_cna | |
| Microsoft/Windows Server 2012 R2 (Server Core installation) Microsoft · Windows Server 2012 R2 (Server Core installation) | affected | >= 6.3.9600.0, < 6.3.9600.23291 | none available | cve_cna | |
| Microsoft/Windows Server 2016 Microsoft · Windows Server 2016 | affected | >= 10.0.14393.0, < 10.0.14393.9339 | none available | cve_cna | |
| Microsoft/Windows Server 2016 (Server Core installation) Microsoft · Windows Server 2016 (Server Core installation) | affected | >= 10.0.14393.0, < 10.0.14393.9339 | none available | cve_cna | |
| Microsoft/Windows Server 2019 Microsoft · Windows Server 2019 | affected | >= 10.0.17763.0, < 10.0.17763.9020 | none available | cve_cna | |
| Microsoft/Windows Server 2019 (Server Core installation) Microsoft · Windows Server 2019 (Server Core installation) | affected | >= 10.0.17763.0, < 10.0.17763.9020 | none available | cve_cna | |
| Microsoft/Windows Server 2022 Microsoft · Windows Server 2022 | affected | >= 10.0.20348.0, < 10.0.20348.5386 | none available | cve_cna | |
| Microsoft/Windows Server 2025 Microsoft · Windows Server 2025 | affected | >= 10.0.26100.0, < 10.0.26100.33158 | none available | cve_cna | |
| Microsoft/Windows Server 2025 (Server Core installation) Microsoft · Windows Server 2025 (Server Core installation) | affected | >= 10.0.26100.0, < 10.0.26100.33158 | none available | cve_cna |
A claim with no version range is shown as written rather than expanded: a government catalog naming only a vendor and product is a real statement at zero granularity, and inventing bounds for it would put precision in the record that the source never offered.