Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY79 SECURITY RECORDS

Microsoft

Windows Server 2008 R2 Service Pack 1

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

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

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2025-24064 11 Mar 2025 6.1.7601.0 < 6.1.7601.27618; 6.0.6003.0 < 6.0.6003.23168; 6.2.9200.0 < 6.2.9200.25368; 6.3.9600.0 < 6.3.9600.22470 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-21410 11 Feb 2025 6.1.7601.0 < 6.1.7601.27566; 6.0.6003.0 < 6.0.6003.23117; 6.2.9200.0 < 6.2.9200.25317; 6.3.9600.0 < 6.3.9600.22417 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-2025-21208 11 Feb 2025 6.1.7601.0 < 6.1.7601.27566; 6.0.6003.0 < 6.0.6003.23117; 6.2.9200.0 < 6.2.9200.25317; 6.3.9600.0 < 6.3.9600.22417 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-2025-21297 14 Jan 2025 6.1.7601.0 < 6.1.7601.27520; 6.2.9200.0 < 6.2.9200.25273; 6.3.9600.0 < 6.3.9600.22371; 10.0.14393.0 < 10.0.14393.7699 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-43456 8 Oct 2024 6.1.7601.0 < 6.1.7601.27366; 6.2.9200.0 < 6.2.9200.25118; 6.3.9600.0 < 6.3.9600.22221; 10.0.14393.0 < 10.0.14393.7428 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-38260 10 Sep 2024 6.1.7601.0 < 6.1.7601.27320; 6.2.9200.0 < 6.2.9200.25073; 6.3.9600.0 < 6.3.9600.22175; 10.0.14393.0 < 10.0.14393.7336 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-30075 11 Jun 2024 6.1.7601.0 < 6.1.7601.27170; 6.0.6003.0 < 6.0.6003.22720 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-30074 11 Jun 2024 6.1.7601.0 < 6.1.7601.27170; 6.0.6003.0 < 6.0.6003.22720 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-2023-35379 8 Aug 2023 6.1.7601.0 < 6.1.7601.26664 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-2023-36876 8 Aug 2023 6.1.7601.0 < 6.1.7601.26664 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-2021-42291 10 Nov 2021 6.1.7601.0 < 6.1.7601.25769; 6.0.6003.0 < 6.0.6003.21282; 6.2.9200.0 < 6.2.9200.23517; 6.3.9600.0 < 6.3.9600.20174 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-2021-42282 10 Nov 2021 6.1.7601.0 < 6.1.7601.25769; 6.0.6003.0 < 6.0.6003.21282; 6.2.9200.0 < 6.2.9200.23517; 6.3.9600.0 < 6.3.9600.20174 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-2021-34444 16 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-34442 16 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-34499 14 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-34494 14 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-33786 14 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-33780 14 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-33764 14 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-33754 14 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-33746 14 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-33745 14 Jul 2021 6.1.7601.0 < 6.1.7601.25661; 6.0.6003.0 < 6.0.6003.21167; 6.2.9200.0 < 6.2.9200.23409; 6.3.9600.0 < 6.3.9600.20069 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-2021-27063 11 Mar 2021 6.1.7601.0 < 6.1.7601.24566; 6.0.6003.0 < 6.0.6003.21070; 6.2.9200.0 < 6.2.9200.23298; 6.3.9600.0 < 6.3.9600.19968 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-2021-26897 11 Mar 2021 6.1.7601.0 < 6.1.7601.24566; 6.0.6003.0 < 6.0.6003.21070; 6.2.9200.0 < 6.2.9200.23298; 6.3.9600.0 < 6.3.9600.19968 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-2021-26896 11 Mar 2021 6.1.7601.0 < 6.1.7601.24566; 6.0.6003.0 < 6.0.6003.21070; 6.2.9200.0 < 6.2.9200.23298; 6.3.9600.0 < 6.3.9600.19968 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-2021-26895 11 Mar 2021 6.1.7601.0 < 6.1.7601.24566; 6.0.6003.0 < 6.0.6003.21070; 6.2.9200.0 < 6.2.9200.23298; 6.3.9600.0 < 6.3.9600.19968 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-2021-26894 11 Mar 2021 6.1.7601.0 < 6.1.7601.24566; 6.0.6003.0 < 6.0.6003.21070; 6.2.9200.0 < 6.2.9200.23298; 6.3.9600.0 < 6.3.9600.19968 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-2021-26893 11 Mar 2021 6.1.7601.0 < 6.1.7601.24566; 6.0.6003.0 < 6.0.6003.21070; 6.2.9200.0 < 6.2.9200.23298; 6.3.9600.0 < 6.3.9600.19968 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-2021-26877 11 Mar 2021 6.1.7601.0 < 6.1.7601.24566; 6.0.6003.0 < 6.0.6003.21070; 6.2.9200.0 < 6.2.9200.23298; 6.3.9600.0 < 6.3.9600.19968 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.