Progress MOVEit Transfer 2024.1 (16.1) · Version Status

Progress MOVEit Transfer 2024.1 (16.1) End of Life Date

Progress MOVEit Transfer 2024.1 (16.1) 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.

⚠ Progress MOVEit Transfer 2024.1 (16.1) is past end of life. This version no longer receives security patches. Past EOL — migrate to a supported version immediately.
EOL Date
date not published
Past EOL
Latest Release
2024.1.8
Standard release
Release Date
Nov 20, 2024
Progress MOVEit Transfer 2024.1 (16.1) series
Lifecycle detail

Progress MOVEit Transfer 2024.1 was released on November 20, 2024. Its most recent patch is 2024.1.8, published November 17, 2025.

← Progress MOVEit Transfer 2024.0 (16.0) All Progress MOVEit Transfer versions Progress MOVEit Transfer 2025.0 (17.0) →
45 / 100
Medium Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/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 →  ·  View score card →
Recommended upgrade path
Progress MOVEit Transfer 2026.0 (18.0)
Latest release: 2026.0.5 · EOL: Nov 17, 2027
View full Progress MOVEit Transfer timeline →
Extended Support
Extended Progress MOVEit Transfer 2024.1 (16.1) support is available

Commercial vendors offer security patches beyond EOL. Compare your options.

Compare Options →
All Progress MOVEit Transfer Versions
VersionLatestEOL DateStatus
2024.0 (16.0) 2024.0.8 Supported EOL
→ 2024.1 (16.1) 2024.1.8 Supported EOL
2025.0 (17.0) 2025.0.8 Nov 18, 2026 Warning
2025.1 (17.1) 2025.1.7 May 19, 2027 Active
2026.0 (18.0) 2026.0.5 Nov 17, 2027 Active

What does Progress MOVEit Transfer 2024.1 (16.1) end of life mean?

When Progress MOVEit Transfer 2024.1 (16.1) 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 Progress MOVEit Transfer 2024.1 (16.1) past its EOL date creates a growing attack surface that a clean scan result does not rule out.

Migrate to Progress MOVEit Transfer 2026.0 (18.0) or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Progress MOVEit Transfer 2024.1 (16.1) reach end of life?
Progress MOVEit Transfer 2024.1 (16.1) has already reached end of life, though the vendor has not published an exact date.
Is Progress MOVEit Transfer 2024.1 (16.1) still supported?
No. Progress MOVEit Transfer 2024.1 (16.1) reached end of life on date not published and is no longer receiving security patches.
What should I upgrade to from Progress MOVEit Transfer 2024.1 (16.1)?
The recommended upgrade from Progress MOVEit Transfer 2024.1 (16.1) is Progress MOVEit Transfer 2026.0 (18.0) — the latest actively supported version. Check the Progress MOVEit Transfer full timeline for all supported versions.
What are the security risks of running Progress MOVEit Transfer 2024.1 (16.1) past EOL?
When Progress MOVEit Transfer 2024.1 (16.1) reaches end of life, the maintainers stop issuing 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 Progress MOVEit Transfer should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →