Plesk · Lifecycle Status

Plesk End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Plesk versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Plesk 18.0.77 reaches end of life on June 23, 2026. Plan your migration now — EOL today.
📅 Get reminded before Plesk 18.0.77 reaches EOL on June 23, 2026 — alerts 90, 30 & 7 days out.
Google →
Latest Active
— series
Next EOL
18.0.77
Jun 23, 2026
Active Versions
0
of 31 total
EOL Versions
29
no longer patched
35 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
25/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
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
Release cycle timeline 20172018201920202021202220232024202520261718.0.4918.0.5018.0.5118.0.5218.0.5318.0.5418.0.5518.0.5618.0.5718.0.5818.0.5918.0.6018.0.6118.0.6218.0.6318.0.6418.0.6518.0.6618.0.6718.0.6818.0.6918.0.7018.0.7118.0.7218.0.7318.0.7418.0.7518.0.7618.0.7718.0.78TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
17 17.8.11.95 Oct 11, 2016 Apr 20, 2021 1890 days past EOL EOL
18.0.49 18.0.49.2 Dec 20, 2022 Mar 12, 2023 1199 days past EOL EOL
18.0.50 18.0.50.2 Jan 31, 2023 Apr 23, 2023 1157 days past EOL EOL
18.0.51 18.0.51.1 Mar 14, 2023 Jun 6, 2023 1113 days past EOL EOL
18.0.52 18.0.52.3 Apr 25, 2023 Jul 18, 2023 1071 days past EOL EOL
18.0.53 18.0.53.2 Jun 6, 2023 Sep 4, 2023 1023 days past EOL EOL
18.0.54 18.0.54.4 Jul 18, 2023 Oct 10, 2023 987 days past EOL EOL
18.0.55 18.0.55.2 Aug 29, 2023 Nov 21, 2023 945 days past EOL EOL
18.0.56 18.0.56.4 Oct 10, 2023 Jan 2, 2024 903 days past EOL EOL
18.0.57 18.0.57.5 Nov 21, 2023 Feb 13, 2024 861 days past EOL EOL
18.0.58 18.0.58.2 Jan 9, 2024 Apr 2, 2024 812 days past EOL EOL
18.0.59 18.0.59.2 Feb 20, 2024 May 15, 2024 769 days past EOL EOL
18.0.60 18.0.60.1 Apr 2, 2024 Jun 25, 2024 728 days past EOL EOL
18.0.61 18.0.61.6 May 14, 2024 Aug 6, 2024 686 days past EOL EOL
18.0.62 18.0.62.2 Jun 25, 2024 Sep 17, 2024 644 days past EOL EOL
18.0.63 18.0.63.4 Aug 6, 2024 Oct 29, 2024 602 days past EOL EOL
18.0.64 18.0.64.1 Sep 17, 2024 Dec 10, 2024 560 days past EOL EOL
18.0.65 18.0.65.2 Oct 29, 2024 Jan 21, 2025 518 days past EOL EOL
18.0.66 18.0.66.2 Dec 10, 2024 Mar 4, 2025 476 days past EOL EOL
18.0.67 18.0.67.3 Jan 21, 2025 Apr 15, 2025 434 days past EOL EOL
18.0.68 18.0.68.2 Mar 4, 2025 May 27, 2025 392 days past EOL EOL
18.0.69 18.0.69.4 Apr 15, 2025 Jul 8, 2025 350 days past EOL EOL
18.0.70 18.0.70.4 May 27, 2025 Aug 19, 2025 308 days past EOL EOL
18.0.71 18.0.71.2 Jul 8, 2025 Sep 30, 2025 266 days past EOL EOL
18.0.72 18.0.72.3 Aug 19, 2025 Nov 11, 2025 224 days past EOL EOL
18.0.73 18.0.73.5 Sep 30, 2025 Dec 23, 2025 182 days past EOL EOL
18.0.74 18.0.74.3 Nov 11, 2025 Feb 3, 2026 140 days past EOL EOL
18.0.75 18.0.75.1 Jan 6, 2026 Mar 31, 2026 84 days past EOL EOL
18.0.76 18.0.76.6 Feb 16, 2026 May 11, 2026 43 days past EOL EOL
18.0.77 18.0.77.5 Mar 31, 2026 Jun 23, 2026 EOL today Warning
18.0.78 18.0.78.4 May 12, 2026 Aug 4, 2026 42 days remaining Warning

What does Plesk end of life mean for your organization?

When a version of Plesk 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 Plesk 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 Plesk 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.

Contact Us →
Frequently Asked Questions
What is the end-of-life date for Plesk?
The next Plesk version reaching EOL is 18.0.77 on June 23, 2026. See the full table above for all version EOL dates.
When is the Plesk support end date?
The next Plesk support end date is June 23, 2026, when version 18.0.77 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 Plesk?
The latest active version of Plesk is . Always verify against the table above as support windows can change.
What happens when Plesk reaches end of life?
When Plesk 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 Plesk?
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 Plesk versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →