Progress MOVEit Automation 2025.0 (17.0) · Version Status
Progress MOVEit Automation 2025.0 (17.0) End of Life Date
Progress MOVEit Automation 2025.0 (17.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 Automation 2025.0 (17.0) reaches end of life on November 18, 2026. Plan your migration now — 40 days remaining.
📅 Get reminded before Progress MOVEit Automation 2025.0 (17.0) reaches EOL on November 18, 2026 — alerts 90, 30 & 7 days out.
✓ Alerts are on — confirmation is in your inbox.
EOL Date
Nov 18, 2026
40 days remaining
Latest Release
2025.0.12
Standard release
Release Date
May 21, 2025
Progress MOVEit Automation 2025.0 (17.0) series
Lifecycle detail
Progress MOVEit Automation 2025.0 was released on May 21, 2025 and support is scheduled to end on November 18, 2026 — a planned supported lifespan of 1 year and 6 months, in line with the 1 year and 6 months median for Progress MOVEit Automation releases. Its most recent patch is 2025.0.12, published May 22, 2026.
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 Progress MOVEit Automation 2025.0 (17.0) support is available
Commercial vendors offer security patches beyond EOL. Compare your options.
Compare Options →
All Progress MOVEit Automation Versions
What does Progress MOVEit Automation 2025.0 (17.0) end of life mean?
When Progress MOVEit Automation 2025.0 (17.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 Automation 2025.0 (17.0) past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to Progress MOVEit Automation 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 Automation 2025.0 (17.0) reach end of life?
Progress MOVEit Automation 2025.0 (17.0) reached end of life on November 18, 2026. That is 40 days remaining.
Is Progress MOVEit Automation 2025.0 (17.0) still supported?
Progress MOVEit Automation 2025.0 (17.0) is still supported but approaching end of life on November 18, 2026. Begin planning your migration now.
What should I upgrade to from Progress MOVEit Automation 2025.0 (17.0)?
The recommended upgrade from Progress MOVEit Automation 2025.0 (17.0) is
Progress MOVEit Automation 2026.0 (18.0) — the latest actively supported version. Check the
Progress MOVEit Automation full timeline for all supported versions.
What are the security risks of running Progress MOVEit Automation 2025.0 (17.0) past EOL?
When Progress MOVEit Automation 2025.0 (17.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 Automation should migrate immediately or implement compensating controls.