Control-M End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Control-M versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
✓Control-M 9.0.22.050 is actively supported. Next EOL: version 9.0.21 on September 8, 2027.
📅 Get reminded before Control-M 9.0.21 reaches EOL on September 8, 2027 — alerts 90, 30 & 7 days out.
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 →
Release Cycle Timeline
■ EOL
■ Warning
■ Active
┊ Today
All Versions
Version
Latest Release
Release Date
EOL Date
Days
Status
9.0.0
9.0.00.200
Jul 15, 2015
Oct 31, 2020
2061 days past EOL
EOL
9.0.18
9.0.18.200
Jan 3, 2018
Mar 31, 2023
1180 days past EOL
EOL
9.0.19
9.0.19.200
Mar 4, 2019
Mar 4, 2024
841 days past EOL
EOL
9.0.20
9.0.20.200
Jul 24, 2020
Jul 23, 2025
335 days past EOL
EOL
9.0.21
9.0.21.300
Sep 8, 2022
Sep 8, 2027
442 days remaining
Active
9.0.22
9.0.22.050
May 19, 2025
May 19, 2030
1426 days remaining
Active
What does Control-M end of life mean for your organization?
When a version of Control-M 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: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Control-M 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.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Control-M versions. This is a bridge, not a permanent solution — plan your migration in parallel.
endoflife.ai
Need Extended Support?
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
The next Control-M version reaching EOL is 9.0.21 on September 8, 2027. See the full table above for all version EOL dates.
When is the Control-M support end date?
The next Control-M support end date is September 8, 2027, when version 9.0.21 reaches end of support. Each version has its own support end date — see the table above for every version's date.
What is the latest supported version of Control-M?
The latest active version of Control-M is 9.0.22.050. Always verify against the table above as support windows can change.
What happens when Control-M reaches end of life?
When Control-M reaches end of life, the vendor stops issuing security patches. Any CVEs disclosed after the EOL date accumulate indefinitely with no patch path — creating an ever-growing attack surface that most vulnerability scanners do not flag.
How do I check if I'm running an EOL version of Control-M?
Check your current version against the table above. If your version's EOL date has passed, you are running unsupported software. You can also use the endoflife.ai Stack Scanner to check your entire dependency file at once.
Is there extended support available for EOL Control-M versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.