← ← Back to all products
Control-M
Active
DevOps & CI/CD Latest Version: 9.0.22.050 Latest Release: Oct 15, 2025
Control-M is a workload automation and orchestration platform by BMC Software for managing business processes.
Versions
6
Latest Version
9.0.22.050
Active Support
2
EOL
4
Lifecycle Timeline
Today ↓
9.0.22
9.0.22
9.0.21
9.0.21
9.0.20
9.0.20
9.0.19
9.0.19
9.0.18
9.0.18
9.0.0
9.0.0
Active SupportSecurity SupportEOL
Versions
| Release | Release Date | Active Support | EOL | Latest Version | LTS | Status |
|---|---|---|---|---|---|---|
| 9.0.22 | May 19, 2025 | May 19, 2028 | May 19, 2030 | 9.0.22.050 | No | Active |
| 9.0.21 | Sep 8, 2022 | Sep 30, 2026 | Sep 8, 2027 | 9.0.21.300 | No | Active |
| 9.0.20 | Jul 24, 2020 | Apr 30, 2024 | Jul 23, 2025 | 9.0.20.200 | No | EOL |
| 9.0.19 | Mar 4, 2019 | Dec 31, 2022 | Mar 4, 2024 | 9.0.19.200 | No | EOL |
| 9.0.18 | Jan 3, 2018 | Mar 31, 2021 | Mar 31, 2023 | 9.0.18.200 | No | EOL |
| 9.0.0 | Jul 15, 2015 | Aug 1, 2018 | Oct 31, 2020 | 9.0.00.200 | No | EOL |
Frequently Asked Questions
Which versions of Control-M have reached end of life?
The following Control-M versions have reached end of life and no longer receive security updates: 9.0.20, 9.0.19, 9.0.18, 9.0.0. It is recommended to upgrade to a supported version.
Is it safe to continue using Control-M 9.0.20?
Control-M 9.0.20 has reached end of life and no longer receives security patches or bug fixes. Continuing to use it may expose your systems to known vulnerabilities. We strongly recommend upgrading to a supported version.
What is the latest version of Control-M?
The latest version of Control-M is 9.0.22.050, released in the 9.0.22 release cycle.
How many versions of Control-M are currently supported?
Control-M currently has 2 actively supported version(s): 9.0.22, 9.0.21.
When does Control-M 9.0.22 reach end of life?
Control-M 9.0.22 is scheduled to reach end of life on May 19, 2030.
What should I do when Control-M reaches end of life?
When a Control-M version reaches end of life, you should: 1) Plan your migration to a supported version as soon as possible. 2) Review the release notes for breaking changes. 3) Test your applications thoroughly in a staging environment. 4) Update your dependencies to ensure compatibility with the new version.