controlm end of life dates — full support timeline
4 of 6 tracked controlm releases have already reached end of life. The dates below are published support dates, not estimates.
Version support timeline
| Release | Released | End of life | Latest | Status |
|---|---|---|---|---|
| 9.0.22 | 2025-05-19 | 2030-05-19 | 9.0.22.050 | supported |
| 9.0.21 | 2022-09-08 | 2027-09-08 | 9.0.21.300 | supported |
| 9.0.20 | 2020-07-24 | 2025-07-23 | 9.0.20.200 | ended |
| 9.0.19 | 2019-03-04 | 2024-03-04 | 9.0.19.200 | ended |
| 9.0.18 | 2018-01-03 | 2023-03-31 | 9.0.18.200 | ended |
| 9.0.0 | 2015-07-15 | 2020-10-31 | 9.0.00.200 | ended |
Who is affected
Anyone running an unsupported controlm release. After end of life a version stops receiving security patches, which typically becomes an audit or compliance finding before it becomes an outage. Upgrading to a supported release is the migration path; the table above shows which releases still qualify.
Source
These dates are maintained by endoflife.date/controlm, an open community dataset that cites vendor announcements. Verify against the vendor before making a compliance decision.
Get told before the next controlm deadline
You are reading this because a controlm release is losing support. The next one will arrive the same way — quietly, months before an auditor finds it. A free weekly email lists every controlm and related deadline as it is announced, with exact dates and primary sources.
Watch controlm deadlines Team monitoring pilot →
Takes about twenty seconds. No account, no card, no tracking.