Checkmk 2.5 · Version Status

Checkmk 2.5 End of Life Date

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

Checkmk 2.5 is actively supported. EOL date: April 28, 2028.
📅 Get reminded before Checkmk 2.5 reaches EOL on April 28, 2028 — alerts 90, 30 & 7 days out.
Google →
EOL Date
Apr 28, 2028
650 days remaining
Latest Release
2.5
Standard release
Release Date
Apr 28, 2026
Checkmk 2.5 series
← Checkmk 2.4 All Checkmk versions
10 / 100
Low Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
0/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in KEV
Extended Support
0/10 Available
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 →  ·  View score card →
All Checkmk Versions
VersionLatestEOL DateStatus
2.2 2.2 Nov 23, 2025 EOL
2.3 2.3 Oct 29, 2026 Warning
2.4 2.4 Nov 6, 2027 Active
2.5 2.5 Apr 28, 2028 Active

What does Checkmk 2.5 end of life mean?

When Checkmk 2.5 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 Checkmk 2.5 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

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

Frequently Asked Questions
When does Checkmk 2.5 reach end of life?
Checkmk 2.5 reached end of life on April 28, 2028. That is 650 days remaining.
Is Checkmk 2.5 still supported?
Yes, Checkmk 2.5 is currently supported. The EOL date is April 28, 2028.
What should I upgrade to from Checkmk 2.5?
The recommended upgrade from Checkmk 2.5 is Checkmk 2.5 — the latest actively supported version. Check the Checkmk full timeline for all supported versions.
What are the security risks of running Checkmk 2.5 past EOL?
When Checkmk 2.5 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 Checkmk should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →