Complete end-of-life dates, support windows, and security status for all Powershell versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 6.0 | 6.0.5 | Jan 20, 2018 | Feb 13, 2019 | 2642 days past EOL | EOL |
| 6.1 | 6.1.6 | Sep 13, 2018 | Sep 28, 2019 | 2415 days past EOL | EOL |
| 6.2 | 6.2.7 | Mar 29, 2019 | Sep 4, 2020 | 2073 days past EOL | EOL |
| 7.0 LTS | 7.0.13 | Mar 4, 2020 | Dec 3, 2022 | 1253 days past EOL | EOL |
| 7.1 | 7.1.7 | Nov 11, 2020 | May 8, 2022 | 1462 days past EOL | EOL |
| 7.2 LTS | 7.2.24 | Nov 8, 2021 | Nov 8, 2024 | 547 days past EOL | EOL |
| 7.3 | 7.3.12 | Nov 9, 2022 | May 8, 2024 | 731 days past EOL | EOL |
| 7.4 LTS | 7.4.15 | Nov 16, 2023 | Nov 10, 2026 | 185 days remaining | Active |
| 7.5 | 7.5.6 | Jan 23, 2025 | Nov 10, 2026 | 185 days remaining | Active |
| 7.6 LTS | 7.6.1 | Mar 18, 2026 | Nov 14, 2028 | 920 days remaining | Active |
When a Powershell version reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Powershell should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →