← Search results
CVE-LINKED INVENTORY17 SECURITY RECORDS
Microsoft
Windows Server 2025
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Windows Server 2025. Use that record for publisher support phases and retirement dates.
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-72928 | 8 Sep 2026 | Windows Server 2025: 10.0.26100.0 < 10.0.26100.33438; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33438 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-49169 | 14 Jul 2026 | Windows Server 2025: 10.0.26100.0 < 10.0.26100.33158; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33158 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2026-34332 | 12 May 2026 | 10.0.26100.0 < 10.0.26100.32860 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-34350 | 12 May 2026 | 10.0.26100.0 < 10.0.26100.32860 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-20830 | 13 Jan 2026 | 10.0.26100.0 < 10.0.26100.32230 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53779 | 12 Aug 2025 | 10.0.26100.0 < 10.0.26100.4946 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2024-38203 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.19043.0 < 10.0.19044.5131; 10.0.22621.0 < 10.0.22621.4460 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43642 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.20348.0 < 10.0.20348.2849; 10.0.22621.0 < 10.0.22621.4460; 10.0.22631.0 < 10.0.22631.4460; 10.0.25398.0 < 10.0.25398.1251 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43641 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.19043.0 < 10.0.19044.5131; 10.0.22621.0 < 10.0.22621.4460 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43639 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.25398.0 < 10.0.25398.1251; 10.0.14393.0 < 10.0.14393.7515 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43629 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.19043.0 < 10.0.19044.5131; 10.0.22621.0 < 10.0.22621.4460 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43621 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.19043.0 < 10.0.19044.5131; 10.0.22621.0 < 10.0.22621.4460 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-38264 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.22621.0 < 10.0.22621.4460; 10.0.22631.0 < 10.0.22631.4460; 10.0.25398.0 < 10.0.25398.1251 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43449 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.19043.0 < 10.0.19044.5131; 10.0.22621.0 < 10.0.22621.4460 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43646 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.19043.0 < 10.0.19044.5131; 10.0.22621.0 < 10.0.22621.4460 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43644 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.19043.0 < 10.0.19044.5131; 10.0.22621.0 < 10.0.22621.4460 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
| CVE-2024-43643 | 12 Nov 2024 | 10.0.26100.0 < 10.0.26100.2314; 10.0.17763.0 < 10.0.17763.6532; 10.0.20348.0 < 10.0.20348.2849; 10.0.19043.0 < 10.0.19044.5131; 10.0.22621.0 < 10.0.22621.4460 | An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. | Update reference ↗ |
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.