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

Microsoft

Windows 11 version 26H1

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-2026-85921 14 Sep 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2956 10.0.28000.2956:Security Update:https://support.microsoft.com/help/5129194 Update reference ↗
CVE-2026-83939 8 Sep 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2954 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-69617 8 Sep 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2954; 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-69544 8 Sep 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2954 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-62799 11 Aug 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2704 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-62775 11 Aug 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2704 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-72971 11 Aug 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2704 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-62772 11 Aug 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2704 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-58529 14 Jul 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2525 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-58634 14 Jul 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2525 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-58633 14 Jul 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2525 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-50428 14 Jul 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2525 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-49173 14 Jul 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2525 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-44804 9 Jun 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2269 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44813 9 Jun 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2269 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44814 9 Jun 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2269 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44807 9 Jun 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2269 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44808 9 Jun 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2269 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-44811 9 Jun 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.2269 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-32224 14 Apr 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-32216 14 Apr 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2026-32195 14 Apr 2026 Windows 11 version 26H1: 10.0.28000.0 < 10.0.28000.1836 No fixed version is explicitly recorded in the structured CVE data. 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.