Controlm · Lifecycle Status

Controlm End of Life (EOL) Dates & Support Timeline

Complete end-of-life dates, support windows, and security status for all Controlm versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.

Controlm 9.0.21.300 is actively supported. Next EOL: version 9.0.21 on September 8, 2027.
Latest Active
9.0.21.300
9.0.21 series
Next EOL
9.0.21
Sep 8, 2027
Active Versions
2
of 6 total
EOL Versions
4
no longer patched
Release Cycle Timeline
EOL   Warning   Active   Today
Release cycle timeline 2016201720182019202020212022202320242025202620272028202920309.0.09.0.189.0.199.0.209.0.219.0.22TODAY
All Versions
VersionLatest ReleaseRelease DateEOL DateDaysStatus
9.0.0 9.0.00.200 Jul 15, 2015 Oct 31, 2020 2016 days past EOL EOL
9.0.18 9.0.18.200 Jan 3, 2018 Mar 31, 2023 1135 days past EOL EOL
9.0.19 9.0.19.200 Mar 4, 2019 Mar 4, 2024 796 days past EOL EOL
9.0.20 9.0.20.200 Jul 24, 2020 Jul 23, 2025 290 days past EOL EOL
9.0.21 9.0.21.300 Sep 8, 2022 Sep 8, 2027 487 days remaining Active
9.0.22 9.0.22.050 May 19, 2025 May 19, 2030 1471 days remaining Active

What does Controlm end of life mean for your organization?

When a Controlm version 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 Controlm 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.

Check your full stack for EOL risk

Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.

Open Stack Scanner →
Frequently Asked Questions
What is the end-of-life date for Controlm?
The next Controlm version reaching EOL is 9.0.21 on September 8, 2027. See the full table above for all version EOL dates.
What is the latest supported version of Controlm?
The latest active version of Controlm is 9.0.21.300. Always verify against the table above as support windows can change.
What happens when Controlm reaches end of life?
When Controlm 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 Controlm?
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 Controlm versions?
Some vendors offer extended support for EOL software. Contact the original vendor or check with enterprise support providers for options.

Related Products

Data from endoflife.date API · endoflife.date · Generated at build time · How we source data →