← Search results
CVE-LINKED INVENTORY41 SECURITY RECORDS
Microsoft
Windows Server 2012 R2
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 2012 R2. 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-61920 | 11 Aug 2026 | Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23338; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23338; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9418; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9418; Windows Server 2019: 10.0.17763.0 < 10.0.17763.9121; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9121; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5499; Windows Server 2025: 10.0.26100.0 < 10.0.26100.33296; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33296 | 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-62715 | 11 Aug 2026 | Windows Server 2012 R2: 6.3.9600.0 < 6.3.9600.23338; Windows Server 2012 R2 (Server Core installation): 6.3.9600.0 < 6.3.9600.23338; Windows Server 2016: 10.0.14393.0 < 10.0.14393.9418; Windows Server 2016 (Server Core installation): 10.0.14393.0 < 10.0.14393.9418; Windows Server 2019: 10.0.17763.0 < 10.0.17763.9121; Windows Server 2019 (Server Core installation): 10.0.17763.0 < 10.0.17763.9121; Windows Server 2022: 10.0.20348.0 < 10.0.20348.5499; Windows Server 2025: 10.0.26100.0 < 10.0.26100.33296; Windows Server 2025 (Server Core installation): 10.0.26100.0 < 10.0.26100.33296 | 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-41095 | 12 May 2026 | 6.3.9600.0 < 6.3.9600.23181; 10.0.14393.0 < 10.0.14393.9140; 10.0.17763.0 < 10.0.17763.8755; 10.0.20348.0 < 10.0.20348.5139; 10.0.25398.0 < 10.0.25398.2330 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2026-33826 | 14 Apr 2026 | 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-2025-58737 | 14 Oct 2025 | 6.3.9600.0 < 6.3.9600.22824; 10.0.14393.0 < 10.0.14393.8519; 10.0.17763.0 < 10.0.17763.7919; 10.0.20348.0 < 10.0.20348.4294; 10.0.25398.0 < 10.0.25398.1913 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-54106 | 9 Sep 2025 | 6.3.9600.0 < 6.3.9600.22774; 10.0.14393.0 < 10.0.14393.8422; 10.0.17763.0 < 10.0.17763.7792; 10.0.20348.0 < 10.0.20348.4171; 10.0.25398.0 < 10.0.25398.1849 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-55231 | 21 Aug 2025 | 6.3.9600.0 < 6.3.9600.22676; 10.0.14393.0 < 10.0.14393.8246; 10.0.17763.0 < 10.0.17763.7558; 10.0.20348.0 < 10.0.20348.3932; 10.0.26100.0 < 10.0.26100.4652 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-49688 | 8 Jul 2025 | 6.3.9600.0 < 6.3.9600.22676; 10.0.14393.0 < 10.0.14393.8246; 10.0.17763.0 < 10.0.17763.7558; 10.0.20348.0 < 10.0.20348.3932; 10.0.25398.0 < 10.0.25398.1732 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-33068 | 10 Jun 2025 | 6.3.9600.0 < 6.3.9600.22620; 10.0.14393.0 < 10.0.14393.8148; 10.0.17763.0 < 10.0.17763.7434; 10.0.20348.0 < 10.0.20348.3807; 10.0.26100.0 < 10.0.26100.4349 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27486 | 8 Apr 2025 | 6.3.9600.0 < 6.3.9600.22523; 10.0.14393.0 < 10.0.14393.7969; 10.0.17763.0 < 10.0.17763.7136; 10.0.20348.0 < 10.0.20348.3453; 10.0.26100.0 < 10.0.26100.3775 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27485 | 8 Apr 2025 | 6.3.9600.0 < 6.3.9600.22523; 10.0.14393.0 < 10.0.14393.7969; 10.0.17763.0 < 10.0.17763.7136; 10.0.20348.0 < 10.0.20348.3453; 10.0.26100.0 < 10.0.26100.3775 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-26652 | 8 Apr 2025 | 6.3.9600.0 < 6.3.9600.22523; 10.0.14393.0 < 10.0.14393.7969; 10.0.17763.0 < 10.0.17763.7136; 10.0.20348.0 < 10.0.20348.3453; 10.0.26100.0 < 10.0.26100.3775 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-21174 | 8 Apr 2025 | 6.3.9600.0 < 6.3.9600.22523; 10.0.14393.0 < 10.0.14393.7969; 10.0.17763.0 < 10.0.17763.7136; 10.0.20348.0 < 10.0.20348.3453; 10.0.26100.0 < 10.0.26100.3775 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27470 | 8 Apr 2025 | 6.3.9600.0 < 6.3.9600.22523; 10.0.14393.0 < 10.0.14393.7969; 10.0.17763.0 < 10.0.17763.7136; 10.0.20348.0 < 10.0.20348.3453; 10.0.26100.0 < 10.0.26100.3775 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-26680 | 8 Apr 2025 | 6.3.9600.0 < 6.3.9600.22523; 10.0.14393.0 < 10.0.14393.7969; 10.0.17763.0 < 10.0.17763.7136; 10.0.20348.0 < 10.0.20348.3453; 10.0.26100.0 < 10.0.26100.3775 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2024-43512 | 8 Oct 2024 | 6.3.9600.0 < 6.3.9600.22221; 10.0.14393.0 < 10.0.14393.7428; 10.0.17763.0 < 10.0.17763.6414; 10.0.20348.0 < 10.0.20348.2762 | 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-38230 | 10 Sep 2024 | 6.3.9600.0 < 6.3.9600.22175; 10.0.14393.0 < 10.0.14393.7336; 10.0.17763.0 < 10.0.17763.6293; 10.0.20348.0 < 10.0.20348.2700 | 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-30083 | 11 Jun 2024 | 6.3.9600.0 < 6.3.9600.22023; 10.0.14393.0 < 10.0.14393.7070; 10.0.17763.0 < 10.0.17763.5936; 10.0.20348.0 < 10.0.20348.2527 | 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-30062 | 11 Jun 2024 | 6.3.9600.0 < 6.3.9600.22023; 10.0.14393.0 < 10.0.14393.7070; 10.0.17763.0 < 10.0.17763.5936; 10.0.20348.0 < 10.0.20348.2527 | 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-34525 | 14 Jul 2021 | 6.3.9600.0 < 6.3.9600.20069; 10.0.14393.0 < 10.0.14393.4530; 10.0.17763.0 < 10.0.17763.2061; 10.0.0 < 10.0.19041.1110; 10.0.0 < 10.0.19042.1110 | 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-31971 | 8 Jun 2021 | 6.3.0 < 6.3.9600.20045; 6.3.0 < 1.0.0.0; 6.2.0 < 6.2.9200.23372; 6.2.0 < 1.0.0.0; 10.0.0 < 10.0.14393.4467; 6.1.0 < 6.1.7601.25632; 6.1.0 < publication; 6.0.0 < 6.0.6003.21137 | 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-2019-0570 | 8 Jan 2019 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2019-0552 | 8 Jan 2019 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8626 | 12 Dec 2018 | (Server Core installation); Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1709 for 32-bit Systems; Version 1709 for ARM64-based Systems; Version 1709 for x64-based Systems; Version 1803 for 32-bit Systems; Version 1803 for ARM64-based Systems | 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-2018-8561 | 14 Nov 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8547 | 14 Nov 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1709 for 32-bit Systems; Version 1709 for x64-based Systems | 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-2018-8485 | 14 Nov 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8476 | 14 Nov 2018 | (Server Core installation); 32-bit Systems Service Pack 2; 32-bit Systems Service Pack 2 (Server Core installation); Itanium-Based Systems Service Pack 2; x64-based Systems Service Pack 2; x64-based Systems Service Pack 2 (Server Core installation); Itanium-Based Systems Service Pack 1; x64-based Systems Service Pack 1 | 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-2018-8493 | 10 Oct 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8484 | 10 Oct 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8320 | 10 Oct 2018 | (Server Core installation); 32-bit Systems Service Pack 2; 32-bit Systems Service Pack 2 (Server Core installation); Itanium-Based Systems Service Pack 2; x64-based Systems Service Pack 2; x64-based Systems Service Pack 2 (Server Core installation); Itanium-Based Systems Service Pack 1; x64-based Systems Service Pack 1 | 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-2018-8455 | 13 Sep 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems; Version 1703 for x64-based Systems | 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-2018-8439 | 13 Sep 2018 | (Server Core installation); Windows RT 8.1; x64-based systems; Version 1607 for x64-based Systems; Version 1703 for x64-based Systems; Version 1709 for x64-based Systems; Version 1803 for x64-based Systems; x64-based Systems | 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-2018-8438 | 13 Sep 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8335 | 13 Sep 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8313 | 11 Jul 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8210 | 14 Jun 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-8134 | 9 May 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1607 for 32-bit Systems; Version 1607 for x64-based Systems; Version 1703 for 32-bit Systems | 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-2018-1009 | 12 Apr 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1511 for 32-bit Systems; Version 1511 for x64-based Systems; Version 1607 for 32-bit Systems | 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-2018-0968 | 12 Apr 2018 | (Server Core installation); Windows RT 8.1; 32-bit systems; x64-based systems; 32-bit Systems; Version 1511 for 32-bit Systems; Version 1511 for x64-based Systems; Version 1607 for 32-bit Systems | 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-2018-0957 | 12 Apr 2018 | (Server Core installation); Windows RT 8.1; x64-based systems; Version 1511 for x64-based Systems; Version 1607 for x64-based Systems; Version 1703 for x64-based Systems; Version 1709 for x64-based Systems; x64-based Systems | 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.