Controlm 9.0.22 · Version Status

Controlm 9.0.22 End of Life Date

Controlm 9.0.22 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Controlm 9.0.22 is actively supported. EOL date: May 19, 2030.
EOL Date
May 19, 2030
1471 days remaining
Latest Release
9.0.22.050
Standard release
Release Date
May 19, 2025
Controlm 9.0.22 series
← Controlm 9.0.21 All Controlm versions
All Controlm Versions
VersionLatestEOL DateStatus
9.0.0 9.0.00.200 Oct 31, 2020 EOL
9.0.18 9.0.18.200 Mar 31, 2023 EOL
9.0.19 9.0.19.200 Mar 4, 2024 EOL
9.0.20 9.0.20.200 Jul 23, 2025 EOL
9.0.21 9.0.21.300 Sep 8, 2027 Active
9.0.22 9.0.22.050 May 19, 2030 Active

What does Controlm 9.0.22 end of life mean?

When Controlm 9.0.22 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: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Controlm 9.0.22 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Controlm 9.0.22 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Controlm 9.0.22 reach end of life?
Controlm 9.0.22 reached end of life on May 19, 2030. That is 1471 days remaining.
Is Controlm 9.0.22 still supported?
Yes, Controlm 9.0.22 is currently supported. The EOL date is May 19, 2030.
What should I upgrade to from Controlm 9.0.22?
The recommended upgrade from Controlm 9.0.22 is Controlm 9.0.22 — the latest actively supported version. Check the Controlm full timeline for all supported versions.
What are the security risks of running Controlm 9.0.22 past EOL?
When Controlm 9.0.22 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Controlm should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →