[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"$fisd34EAl9eU7X4hDVrrLmt9wDk479HZKZ2cit4F2vWw":3},{"product":4,"cycleMajor":13,"releases":14,"cves":22,"nextMajor":9,"indexable":39},{"id":5,"slug":6,"name":7,"category":8,"vendor":9,"description":10,"logo_url":9,"official_url":9,"synced_at":11,"created_at":12},"8afb5419-a4a5-4396-894d-2afbb2731e20","windows","Windows","os",null,"Developers rely on accurate and timely information to manage their systems and ensure security, which is why tracking Windows end-of-life dates is crucial. Windows, first released in 1985, has become a widely used operating system, with Microsoft maintaining and supporting its various versions. The complexity of managing multiple Windows versions can be overwhelming, but having a clear understanding of the supported versions and their respective timelines is essential for planning upgrades and minimizing potential security risks.\n\nThe Windows ecosystem consists of 47 total versions, with 34 of them having already reached their end-of-life, leaving 13 active versions that still receive support and security updates. The latest stable version, 10.0.14393, is still supported, but developers should be aware that version 10-1607-e-lts is next in line to expire, with its end-of-life date set for October 13, 2026. This information is vital for planning and executing upgrades, as well as ensuring that systems remain secure and compliant. The most recent version to reach its end-of-life was 11-23h2-w, which occurred on November 11, 2025.\n\nThe security landscape for Windows is constantly evolving, with a total of 47 tracked CVEs, although none of them are currently classified as critical. The most affected version is 10-20h2-e, with a single reported CVE. Despite the lack of critical vulnerabilities, it is essential for developers to remain vigilant and take proactive measures to secure their systems. This includes regularly reviewing and updating their Windows versions to ensure they have the latest security patches and are not exposed to potential risks. By staying informed about Windows end-of-life dates and security patch timelines, developers can effectively manage their systems and maintain the highest level of security.","2026-10-07T02:00:11.307+00:00","2026-05-30T16:23:56.027772+00:00","10-20h2-e",[15],{"id":16,"product_id":5,"cycle":13,"release_date":17,"eol":18,"eol_boolean":9,"latest":19,"latest_release_date":9,"lts":20,"support":18,"created_at":21},"06b05410-1a14-4bb7-b330-b3f96fbed84b","2020-10-20","2023-05-09","10.0.19042",false,"2026-05-30T16:26:03.701812+00:00",[23,31],{"cveId":24,"releaseId":16,"cycle":13,"description":25,"severity":26,"cvssScore":27,"epssScore":28,"inKev":20,"publishedAt":29,"url":30},"CVE-2021-36958","A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged file operations. An attacker who successfully exploited this vulnerability could run arbitrary code with SYSTEM privileges. An attacker could then install programs; view, change, or delete data; or create new accounts with full user rights.","HIGH",7.8,0.30794,"2021-08-12T18:15:10.303+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-2021-36958",{"cveId":32,"releaseId":16,"cycle":13,"description":33,"severity":34,"cvssScore":35,"epssScore":36,"inKev":20,"publishedAt":37,"url":38},"CVE-1999-0524","ICMP information such as (1) netmask and (2) timestamp is allowed from arbitrary hosts.","MEDIUM",4,0.32154,"1997-08-01T04:00:00+00:00","https:\u002F\u002Fnvd.nist.gov\u002Fvuln\u002Fdetail\u002FCVE-1999-0524",true]