Checkmk Lifecycle policy

Checkmk is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Evidence status

This record passed BlackTree's automatic primary-source checks with a confidence score of 82. It is returned for operational research without requiring routine manual approval. Confirm edition and deployment applicability before acting.

This discovery does not establish a product-specific support or retirement date. A missing date does not mean support continues.

Product overview

Checkmk is tracked by BlackTree as a server-side software product. Its lifecycle page separates release identity, maintenance and security boundaries using the publisher's registered source.

Main capabilities

Networked or application service delivery
Administrative and operational interfaces
Versioned maintenance and security updates

Typical use

Used to provide application, infrastructure or operational services to other systems and users.

Deployment

Deployed on servers, virtual machines, containers or managed infrastructure.

This category-level context is generated from the registered product identity. Confirm exact product capabilities on the publisher's page .

Collected lifecycle data

Product	Checkmk
Release	Lifecycle policy
Start or release	Not extracted
Lifecycle boundary	Continuous or not dated in the source
Date precision	Unknown

Known exploited vulnerabilities

Catalogue updated 29 Sep 2026

These are product-family matches in the CISA Known Exploited Vulnerabilities catalogue. Confirm the affected product version in the vendor advisory.

No CISA known-exploited entries currently match this mapped product family.

This does not mean the product has no vulnerabilities.

Package vulnerability advisories

Checked 29 Sep 2026

OSV advisories are matched through the registered package URL. A package-family match does not prove that the installed release is affected. Check the affected and fixed versions before remediation.

No package advisories have been linked for this product identity.

This is not evidence that the product has no vulnerabilities.

Source evidence

PRIMARYManual

Checkmk official lifecycle source

4.2. Passive maintenance | After the end of the active maintenance, the stable branch moves to a passive maintenance phase, which generally lasts for another year. | During this time we generally only fix errors when commissioned by customers using support tickets through a support contract. | However, there is no guarantee that everything that users might consider a bug will be fixed. Also, not all bug fixes will be ported to the oldest versions. This is especially true for features that are considered deprecated—these will generally not receive bug fixes. | Bug fixes during the passive maintenance phase generate further patch versions, which are of course also beneficial to users without a support contract. | 4.3. Product lifecycle of the stable versions | Whether your version is still being maintained and when it has reached or will reach its end-of-life can be seen from the following table:

Publisher identity used by product-specific official-source collectors.

First collected 12 Sep 2026 · Last collected 29 Sep 2026 · Review state accepted

Open official vendor source