← Search results
CVE-LINKED INVENTORY218 SECURITY RECORDS
Microsoft
Windows 11 Version 24H2
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 11 version 24H2. 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-2025-62572 | 9 Dec 2025 | 10.0.26100.0 < 10.0.26100.7462; 10.0.26200.0 < 10.0.26200.7462 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-62469 | 9 Dec 2025 | 10.0.26100.0 < 10.0.26100.7462; 10.0.26200.0 < 10.0.26200.7462 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-60721 | 11 Nov 2025 | 10.0.26100.0 < 10.0.26100.7171; 10.0.26200.0 < 10.0.26200.7171 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-60718 | 11 Nov 2025 | 10.0.26100.0 < 10.0.26100.7171; 10.0.26200.0 < 10.0.26200.7171 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59241 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-59210 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-59189 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55698 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55694 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899; 10.0.25398.0 < 10.0.25398.1913 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55693 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55691 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55690 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55688 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55684 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55682 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55337 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-59257 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899; 10.0.25398.0 < 10.0.25398.1913 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-59206 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55677 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-55676 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-50174 | 14 Oct 2025 | 10.0.26100.0 < 10.0.26100.6899; 10.0.26200.0 < 10.0.26200.6899 | No fixed version is explicitly recorded in the structured CVE data. | Update reference ↗ |
| CVE-2025-59216 | 18 Sep 2025 | 10.0.26100.0 < 10.0.26100.6584 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-59215 | 18 Sep 2025 | 10.0.26100.0 < 10.0.26100.6584 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-54108 | 9 Sep 2025 | 10.0.26100.0 < 10.0.26100.6584 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-54105 | 9 Sep 2025 | 10.0.26100.0 < 10.0.26100.6584; 10.0.25398.0 < 10.0.25398.1849 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53809 | 9 Sep 2025 | 10.0.26100.0 < 10.0.26100.6584 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53156 | 12 Aug 2025 | 10.0.26100.0 < 10.0.26100.4946; 10.0.25398.0 < 10.0.25398.1791 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-53133 | 12 Aug 2025 | 10.0.26100.0 < 10.0.26100.4946 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-50169 | 12 Aug 2025 | 10.0.26100.0 < 10.0.26100.4946 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-50165 | 12 Aug 2025 | 10.0.26100.0 < 10.0.26100.4946 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-48810 | 8 Jul 2025 | 10.0.26100.0 < 10.0.26100.4652 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-48809 | 8 Jul 2025 | 10.0.26100.0 < 10.0.26100.4652 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-48002 | 8 Jul 2025 | 10.0.26100.0 < 10.0.26100.4652 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-47993 | 8 Jul 2025 | 10.0.26100.0 < 10.0.26100.4652; 10.0.25398.0 < 10.0.25398.1732 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-49694 | 8 Jul 2025 | 10.0.26100.0 < 10.0.26100.4652; 10.0.25398.0 < 10.0.25398.1732 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-26636 | 8 Jul 2025 | 10.0.26100.0 < 10.0.26100.4652 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-33069 | 10 Jun 2025 | 10.0.26100.0 < 10.0.26100.4349 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-29955 | 13 May 2025 | 10.0.26100.0 < 10.0.26100.4061; 10.0.25398.0 < 10.0.25398.1611 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-29838 | 13 May 2025 | 10.0.26100.0 < 10.0.26100.4061 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-29970 | 13 May 2025 | 10.0.26100.0 < 10.0.26100.4061; 10.0.25398.0 < 10.0.25398.1611 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-27728 | 8 Apr 2025 | 10.0.26100.0 < 10.0.26100.3775 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-21179 | 11 Feb 2025 | 10.0.26100.0 < 10.0.26100.3194 | 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-21183 | 11 Feb 2025 | 10.0.26100.0 < 10.0.26100.3194 | 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-21182 | 11 Feb 2025 | 10.0.26100.0 < 10.0.26100.3194 | 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-21379 | 11 Feb 2025 | 10.0.26100.0 < 10.0.26100.3194 | 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-21311 | 14 Jan 2025 | 10.0.26100.0 < 10.0.26100.2894; 10.0.25398.0 < 10.0.25398.1369 | 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-21313 | 14 Jan 2025 | 10.0.26100.0 < 10.0.26100.2894; 10.0.25398.0 < 10.0.25398.1369 | No fixed version is explicitly recorded in the structured CVE data. | Use CVE record |
| CVE-2025-21372 | 14 Jan 2025 | 10.0.26100.0 < 10.0.26100.2894; 10.0.25398.0 < 10.0.25398.1369 | 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-21315 | 14 Jan 2025 | 10.0.26100.0 < 10.0.26100.2894; 10.0.25398.0 < 10.0.25398.1369 | 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-49093 | 10 Dec 2024 | 10.0.26100.0 < 10.0.26100.2605 | 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.