Progress MOVEit Transfer 2026.0 (18.0) · Version Status

Progress MOVEit Transfer 2026.0 (18.0) End of Life Date

Progress MOVEit Transfer 2026.0 (18.0) 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 2026.0 (18.0) is actively supported. EOL date: November 17, 2027.
📅 Get reminded before Progress MOVEit Transfer 2026.0 (18.0) reaches EOL on November 17, 2027 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Nov 17, 2027
404 days remaining
Latest Release
2026.0.5
Standard release
Release Date
May 20, 2026
Progress MOVEit Transfer 2026.0 (18.0) series
Lifecycle detail

Progress MOVEit Transfer 2026.0 was released on May 20, 2026 and support is scheduled to end on November 17, 2027 — a planned supported lifespan of 1 year and 6 months, in line with the 1 year and 6 months median for Progress MOVEit Transfer releases. Its most recent patch is 2026.0.5, published September 24, 2026.

← Progress MOVEit Transfer 2025.1 (17.1) All Progress MOVEit Transfer versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/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 →
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 2026.0 (18.0) end of life mean?

When Progress MOVEit Transfer 2026.0 (18.0) 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 2026.0 (18.0) 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 2026.0 (18.0) reach end of life?
Progress MOVEit Transfer 2026.0 (18.0) reached end of life on November 17, 2027. That is 404 days remaining.
Is Progress MOVEit Transfer 2026.0 (18.0) still supported?
Yes, Progress MOVEit Transfer 2026.0 (18.0) is currently supported. The EOL date is November 17, 2027.
What should I upgrade to from Progress MOVEit Transfer 2026.0 (18.0)?
The recommended upgrade from Progress MOVEit Transfer 2026.0 (18.0) 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 2026.0 (18.0) past EOL?
When Progress MOVEit Transfer 2026.0 (18.0) 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 →