Powershell 6.1 · Version Status
Powershell 6.1 End of Life Date
Powershell 6.1 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Powershell 6.1 is past end of life. This version no longer receives security patches. 2415 days past EOL — migrate to a supported version immediately.
EOL Date
Sep 28, 2019
2415 days past EOL
Latest Release
6.1.6
Standard release
Release Date
Sep 13, 2018
Powershell 6.1 series
| Version | Latest | EOL Date | Status |
| 6.0 |
6.0.5 |
Feb 13, 2019 |
EOL |
| → 6.1 |
6.1.6 |
Sep 28, 2019 |
EOL |
| 6.2 |
6.2.7 |
Sep 4, 2020 |
EOL |
| 7.0 LTS |
7.0.13 |
Dec 3, 2022 |
EOL |
| 7.1 |
7.1.7 |
May 8, 2022 |
EOL |
| 7.2 LTS |
7.2.24 |
Nov 8, 2024 |
EOL |
| 7.3 |
7.3.12 |
May 8, 2024 |
EOL |
| 7.4 LTS |
7.4.15 |
Nov 10, 2026 |
Active |
What does Powershell 6.1 end of life mean?
When Powershell 6.1 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Powershell 6.1 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Powershell 7.6 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Powershell 6.1 reach end of life?
Powershell 6.1 reached end of life on September 28, 2019. This version is no longer receiving security patches.
Is Powershell 6.1 still supported?
No. Powershell 6.1 reached end of life on September 28, 2019 and is no longer receiving security patches.
What should I upgrade to from Powershell 6.1?
The recommended upgrade from Powershell 6.1 is
Powershell 7.6 — the latest actively supported version. Check the
Powershell full timeline for all supported versions.
What are the security risks of running Powershell 6.1 past EOL?
When Powershell 6.1 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Powershell should migrate immediately or implement compensating controls.