Plesk 17 · Version Status
Plesk 17 End of Life Date
Plesk 17 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Plesk 17 is past end of life. This version no longer receives security patches. 2027 days past EOL — migrate to a supported version immediately.
EOL Date
Apr 20, 2021
2027 days past EOL
Latest Release
17.8.11.95
Standard release
Release Date
Oct 11, 2016
Plesk 17 series
Where these dates come from
End of lifeApr 20, 2021endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees ReleaseOct 11, 2016endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Plesk 17 was released on October 11, 2016 and support ended on April 20, 2021 — a supported lifespan of 4 years and 6 months, longer than the 3 months median for Plesk releases. Its latest release on record is 17.8.11.95, published January 25, 2021 — 3 months before support ended. It has been past its end-of-life date for 5 years and 7 months. 34 newer Plesk releases have shipped since.
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 → ·
View score card →
Extended Support
Extended Plesk 17 support options
Some vendors and third parties sell security patches beyond end of life; whether one covers this version varies. Compare your options.
Compare Options →
| Version | Latest | EOL Date | Status |
|---|
| → 17 |
17.8.11.95 |
Apr 20, 2021 |
EOL |
| 18.0.49 |
18.0.49.2 |
Mar 14, 2023 |
EOL |
| 18.0.50 |
18.0.50.2 |
Apr 25, 2023 |
EOL |
| 18.0.51 |
18.0.51.1 |
Jun 6, 2023 |
EOL |
| 18.0.52 |
18.0.52.3 |
Jul 18, 2023 |
EOL |
| 18.0.53 |
18.0.53.2 |
Aug 29, 2023 |
EOL |
| 18.0.54 |
18.0.54.4 |
Oct 10, 2023 |
EOL |
| 18.0.55 |
18.0.55.2 |
Nov 21, 2023 |
EOL |
What does Plesk 17 end of life mean?
When Plesk 17 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Plesk 17 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Plesk 18.0.82 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Plesk 17 reach end of life?
Plesk 17 reached end of life on April 20, 2021. This version is no longer receiving security patches.
Is Plesk 17 still supported?
No. Plesk 17 reached end of life on April 20, 2021 and is no longer receiving security patches.
What should I upgrade to from Plesk 17?
The recommended upgrade from Plesk 17 is
Plesk 18.0.82 — the latest actively supported version. Check the
Plesk full timeline for all supported versions.
What are the security risks of running Plesk 17 past EOL?
Since Plesk 17 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Plesk should migrate immediately or implement compensating controls.