Unsupported Windows Operating System
Hosts run a Windows release that Microsoft no longer supports, so vulnerabilities discovered in it are never fixed.
| Severity | Critical |
| CVSS 3.1 | 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Open in the calculator |
| CVSS 4.0 | 9.3 CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator |
| CWE | CWE-1104: Use of Unmaintained Third Party Components |
| OWASP Top 10 | A03:2025 Software Supply Chain Failures |
| MITRE ATT&CK | T1210 Exploitation of Remote Services, T1068 Exploitation for Privilege Escalation, T1203 Exploitation for Client Execution |
| Category | Outdated Components |
Description
One or more hosts run a release or edition of Windows that has passed the end of its support lifecycle. Once a release reaches end of support, Microsoft stops publishing security updates for it, except to organisations that pay for Extended Security Updates (ESU) where Microsoft offers them for that release. Such hosts usually also lack updates released before the end of support, and they lack security features that later releases enable by default.
Every Windows vulnerability disclosed after the end of support therefore remains permanently unfixed on these hosts, including remotely exploitable flaws in network services and privilege escalation flaws that turn any foothold into full control of the host. Because later releases share much of the same code, the details published with each monthly update for supported releases often show attackers where the unsupported release is also vulnerable, and an attacker on the same network can often compromise such a host with public exploit code and no credentials, then use it as a base for credential theft, lateral movement and ransomware deployment. As no fix will be released, the exposure grows over time, and current security products may also stop supporting the platform. The impact is greatest where the host holds sensitive data, is reachable from untrusted networks, or is trusted by other systems.
Unsupported hosts are identified from the operating system version reported by authenticated scans, by fingerprinting SMB, RDP and other services during unauthenticated scans, and from Active Directory, whose computer objects record the operating system of every domain-joined host. Common causes are servers hosting a legacy application that has not been migrated, specialist equipment controlled by an embedded Windows computer, such as laboratory, manufacturing or medical devices, and hosts left running after a migration. Hosts covered by a current ESU subscription still receive security updates for its term, which should be checked before the finding is reported.
Remediation
Remove unsupported Windows releases from the estate:
- Upgrade or replace each affected host with a supported Windows release, migrating the application or function it provides. Use Microsoft's lifecycle pages to confirm support dates and plan future migrations well before the next end-of-support date.
- Where a migration cannot be completed before support ends, subscribe to Extended Security Updates where Microsoft offers them for that release and install the ESU updates every month. ESU is time-limited and buys time to migrate; it is not a replacement for migration.
- For a host that must remain, such as one that controls specialist equipment, isolate it: place it in its own network segment, allow only the connections it needs, block internet access, email and web browsing from it, disable unused services and monitor it closely, as the NCSC's guidance on obsolete products describes.
- Record each remaining unsupported host as an accepted risk with an owner and a replacement date, and review the decision regularly.
Confirm the fix by checking the operating system version of each host in a new authenticated scan and in Active Directory.
References
Add This Finding to Your Library
In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.
Free trialYour trial starts when your portal goes live, not when you sign up, so the time you spend setting up does not count. · No card required
Only need the reporting? Our reporting tool is free and open source, with the same library.