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 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. The last patch it will ever receive is 17.8.11.95, published January 25, 2021 — 3 months before support ended. It has been without security patches for 5 years and 5 months. 33 newer Plesk releases have shipped since.
Commercial vendors offer security patches beyond EOL. 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 12, 2023 | EOL |
| 18.0.50 | 18.0.50.2 | Apr 23, 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 | Sep 4, 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 a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.