PowerShell End of Life (EOL) Dates & Support Timeline
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.
⚡PowerShell 7.5 reaches end of life on November 10, 2026. Plan your migration now — 140 days remaining.
📅 Get reminded before PowerShell 7.5 reaches EOL on November 10, 2026 — alerts 90, 30 & 7 days out.
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build. Methodology →
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
Version
Latest Release
Release Date
EOL Date
Days
Status
6.0
6.0.5
Jan 20, 2018
Feb 13, 2019
2687 days past EOL
EOL
6.1
6.1.6
Sep 13, 2018
Sep 28, 2019
2460 days past EOL
EOL
6.2
6.2.7
Mar 29, 2019
Sep 4, 2020
2118 days past EOL
EOL
7.0 LTS
7.0.13
Mar 4, 2020
Dec 3, 2022
1298 days past EOL
EOL
7.1
7.1.7
Nov 11, 2020
May 8, 2022
1507 days past EOL
EOL
7.2 LTS
7.2.24
Nov 8, 2021
Nov 8, 2024
592 days past EOL
EOL
7.3
7.3.12
Nov 9, 2022
May 8, 2024
776 days past EOL
EOL
7.4 LTS
7.4.17
Nov 16, 2023
Nov 10, 2026
140 days remaining
Warning
7.5
7.5.8
Jan 23, 2025
Nov 10, 2026
140 days remaining
Warning
7.6 LTS
7.6.3
Mar 18, 2026
Nov 14, 2028
875 days remaining
Active
What does PowerShell end of life mean for your organization?
When a version of PowerShell 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL PowerShell versions. This is a bridge, not a permanent solution — plan your migration in parallel.
endoflife.ai
Need Extended Support?
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
The next PowerShell version reaching EOL is 7.5 on November 10, 2026. See the full table above for all version EOL dates.
When is the PowerShell support end date?
The next PowerShell support end date is November 10, 2026, when version 7.5 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of PowerShell?
The latest active version of PowerShell is 7.6.3. Always verify against the table above as support windows can change.
What happens when PowerShell reaches end of life?
When PowerShell reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of PowerShell?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL PowerShell versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.