Progress WS_FTP Server End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Progress WS_FTP Server versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Progress WS_FTP Server 2025 (10.0) is supported until June 9, 2028, its end-of-support date. Active support for Progress WS_FTP Server 2025 (10.0) ends on December 10, 2027; security fixes continue until that end-of-life date. The next Progress WS_FTP Server version to reach end of life is 2024 (9.0), on April 23, 2027. 1 of 3 tracked Progress WS_FTP Server versions is past end of life; the most recent to reach it, 2022 (8.8), did so on July 4, 2026. The full Progress WS_FTP Server lifecycle, with every version's release and end-of-support date, is in the table below.
Running an EOL version? Get matched with support options — free ↓| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 2022 (8.8) | 8.8.12 | Dec 6, 2022 | Jul 4, 2026 | 97 days past EOL | EOL |
| 2024 (9.0) | 9.0.7 | Oct 23, 2024 | Apr 23, 2027 | 196 days remaining | Active |
| 2025 (10.0) | 10.0.4 | Dec 10, 2025 | Jun 9, 2028 | 609 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/progress-ws-ftp-server)
Progress WS_FTP Server lifecycle status — the real story
Progress WS_FTP Server is a file transfer server. Progress names each release twice, with a year and a version number (WS_FTP Server 2022 is 8.8, 2024 is 9.0, 2025 is 10.0), and publishes Active, Sunset and Retired dates on its WS_FTP Product Support Lifecycle page, with the same phase rules as MOVEit: no service packs or hot fixes in Sunset, and only best-effort support with no product updates once Retired. Releases not listed there are considered retired. WS_FTP Server 2022 (8.8) reached its Retired date on July 4, 2026.
CVE-2023-40044, a deserialization flaw in WS_FTP Server, was added to CISA's Known Exploited Vulnerabilities catalog on October 5, 2023 and is flagged as used in ransomware campaigns. It is the only WS_FTP entry in the catalog (2026.10.08).
Field mapping: support is the vendor's SUNSET date and eol is the vendor's RETIRED date, both exactly as printed. Release dates come from the WS_FTP Server release notes, not the lifecycle page, because the lifecycle page says "The Active phase starts during the month listed. The actual day varies based on the release schedule." For 2022 (8.8), the release notes give December 6, 2022, while the lifecycle page prints 1/4/2023.
Progress WS_FTP Server release and support pattern
Across the 3 release lines with a published release date, Progress WS_FTP Server has shipped a new line roughly every 1.5 years (median interval). A line typically stays supported for about 2.5 years from its release to its end-of-life date.
Of the 3 release lines tracked, 1 is past end of life and 2 are still within support. The newest line, 10.0, was released December 10, 2025. The next scheduled end of life is 9.0 on April 23, 2027 — 195 days from this build. The longest-supported line currently published is 10.0, to June 9, 2028.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Progress WS_FTP Server end of life mean for your organization?
When a version of Progress WS_FTP Server 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: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Progress WS_FTP Server 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.
Your options when Progress WS_FTP Server reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Buy extended support | Migration is genuinely underway but cannot finish before the deadline, or the workload is frozen by certification or a third-party application | A bridge, not a destination — every year purchased is a year the migration still has to happen |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Formalizing decisions like this across your estate? Our free EOL policy template is a ready-to-adopt policy with risk tiers, remediation SLAs, and audit mapping — no signup, free to use and share.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Progress WS_FTP Server versions. This is a bridge, not a permanent solution — plan your migration in parallel.
Progress WS_FTP Server has 1 version past end of life — security patches have stopped, but CVE disclosures haven't. Extended support past the official date exists for many products in this position — whether it exists for Progress WS_FTP Server is exactly what we check. Tell us where to reach you and we'll reply with matched options and pricing guidance — or an honest "no vendor covers this."