← Search results
CVE-LINKED INVENTORY1319 SECURITY RECORDS
Microsoft
Windows 10 Version 1607
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.
A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.
CVE-observed version history
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2026-27917 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23132; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23132; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-27915 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23132; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23132; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-27908 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23132; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23132; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26180 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23132; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23132; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26175 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26174 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23132; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23132; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26167 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26162 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23132; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23132; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26160 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23132; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23132; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26155 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26151 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2012: 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 (Server Core installation): 6.2.9200.0 < 6.2.9200.26026; Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23132; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23132; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-23670 | 14 Apr 2026 | Windows 10 Version 1607: 10.0.14393.0 < 10.0.14393.9060; Windows 10 Version 1809: 10.0.17763.0 < 10.0.17763.8644; Windows 10 Version 21H2: 10.0.19044.0 < 10.0.19044.7184; Windows 10 Version 22H2: 10.0.19045.0 < 10.0.19045.7184; Windows 11 version 22H3: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 23H2: 10.0.22631.0 < 10.0.22631.6936; Windows 11 Version 24H2: 10.0.26100.0 < 10.0.26100.8246; Windows 11 Version 25H2: 10.0.26200.0 < 10.0.26200.8246; Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9060; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9060; Windows Server 2019: 10.0.17763.0 < 10.0.17763.8644; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.8644; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5020; Windows Server 2022, 23H2 Edition (Server Core installation): 10.0.25398.0 < 10.0.25398.2274; Windows Server 2025: 10.0.26100.0 < 10.0.26100.32690; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.32690 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-23674 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26128 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-26111 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25190 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25188 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25187 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25186 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25185 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25181 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25179 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25178 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25177 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25176 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25175 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 6.2.9200.0 < 6.2.9200.25973 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25174 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25173 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25172 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25171 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25169 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25168 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-25165 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-24297 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 6.2.9200.0 < 6.2.9200.25973; 6.3.9600.0 < 6.3.9600.23074 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-24296 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-24295 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-24294 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-24291 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-24289 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-24282 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-23673 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-23672 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-23671 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-23669 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 10.0.26100.0 < 10.0.26100.8037; 10.0.26200.0 < 10.0.26200.8037 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-23668 | 10 Mar 2026 | 10.0.14393.0 < 10.0.14393.8957; 10.0.17763.0 < 10.0.17763.8511; 10.0.19044.0 < 10.0.19044.7058; 10.0.19045.0 < 10.0.19045.7058; 10.0.22631.0 < 10.0.22631.6783; 6.2.9200.0 < 6.2.9200.25973 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2026-21222 | 10 Feb 2026 | 10.0.14393.0 < 10.0.14393.8868; 10.0.17763.0 < 10.0.17763.8389; 10.0.19044.0 < 10.0.19044.6937; 10.0.19045.0 < 10.0.19045.6937; 10.0.22631.0 < 10.0.22631.6649; 10.0.26100.0 < 10.0.26100.7840; 6.3.9600.0 < 6.3.9600.23022 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-21231 | 10 Feb 2026 | 10.0.14393.0 < 10.0.14393.8868; 10.0.17763.0 < 10.0.17763.8389; 10.0.19044.0 < 10.0.19044.6937; 10.0.19045.0 < 10.0.19045.6937; 10.0.22631.0 < 10.0.22631.6649; 10.0.26100.0 < 10.0.26100.7840; 10.0.26200.0 < 10.0.26200.7840 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-21238 | 10 Feb 2026 | 10.0.14393.0 < 10.0.14393.8868; 10.0.17763.0 < 10.0.17763.8389; 10.0.19044.0 < 10.0.19044.6937; 10.0.19045.0 < 10.0.19045.6937; 10.0.22631.0 < 10.0.22631.6649; 10.0.26100.0 < 10.0.26100.7840; 10.0.26200.0 < 10.0.26200.7840 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-21239 | 10 Feb 2026 | 10.0.14393.0 < 10.0.14393.8868; 10.0.17763.0 < 10.0.17763.8389; 10.0.19044.0 < 10.0.19044.6937; 10.0.19045.0 < 10.0.19045.6937; 10.0.22631.0 < 10.0.22631.6649; 10.0.26100.0 < 10.0.26100.7840; 10.0.26200.0 < 10.0.26200.7840 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-21244 | 10 Feb 2026 | 10.0.14393.0 < 10.0.14393.8868; 10.0.17763.0 < 10.0.17763.8389; 10.0.19044.0 < 10.0.19044.6937; 10.0.19045.0 < 10.0.19045.6937; 10.0.22631.0 < 10.0.22631.6649; 10.0.26100.0 < 10.0.26100.7840; 10.0.26200.0 < 10.0.26200.7840 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
How this record is maintained
The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.