Dear friends of Checkmk,
the new stable release 2.5.0p5 of Checkmk is ready for download.
This stable release ships with 5 changes affecting all editions of Checkmk,
0 changes for all commercial editions, 0 Ultimate specific and
0 Ultimate with multi-tenancy specific changes.
Support periods can be found here: Checkmk versions
Changes in all Checkmk editions:
Setup
17993 SEC: Fix XSS in service discovery active check output…
17992 SEC: Fix stored XSS in global settings change log…
20002 SEC: XSS in urls…
User interface
17991 SEC: Fix stored XSS in URL dashboard widget via dangerous URI schemes…
19815 SEC: User Messages widget leaked issuer messages on shared dashboards…
Changes in Checkmk commercial editions:
NO CHANGES
Changes in Checkmk Ultimate:
NO CHANGES
Changes in Checkmk Cloud:
NO CHANGES
Changes in Checkmk Ultimate with multi-tenancy:
NO CHANGES
You can download Checkmk from our download page: https://checkmk.com/download
List of all changes: https://checkmk.com/werks?product=cmk&version=2.5.0p5
We greatly thank you for using Checkmk and wish you a suultimatessful monitoring,
Your Checkmk Team
At this point, can’t we just drop the “0”? I haven’t seen a release that wasn’t x.y.0pz in years.
3 Likes
Me neither
It likely breaks too many scripts everywhere, which assume a x.y.z structure. That’s why at least some mentioned that we shouldn’t do this.
1 Like
Gcon
(Gavin Owen)
June 8, 2026, 2:42pm
4
This update did not go smoothly. I’m using Community Edition with Docker, upgrading from the previous version.
Following the logs I see the container constantly restarting due to a failed service.
cmk exited with code 2 (restarting)
cmk | 2026-06-08T14:35:39.223424993Z Site timezone set to Australia/Sydney
cmk | 2026-06-08T14:35:39.223451059Z ### STARTING XINETD
cmk | 2026-06-08T14:35:39.261841001Z * Starting internet superserver xi[ OK ]
cmk | 2026-06-08T14:35:39.262226294Z ### STARTING SITE
cmk | 2026-06-08T14:35:39.844844525Z Starting agent-receiver…OK
cmk | 2026-06-08T14:35:40.821501627Z Starting mkeventd (builtin: syslog-udp,syslog-tcp,snmptrap)…failed
cmk | 2026-06-08T14:35:40.832759764Z Starting rrdcached…OK
cmk | 2026-06-08T14:35:40.932467657Z Starting redis…OK
cmk | 2026-06-08T14:35:40.951637956Z Starting npcd…OK
cmk | 2026-06-08T14:35:42.555150638Z Starting automation-helper…OK
cmk | 2026-06-08T14:35:44.471124529Z Starting ui-job-scheduler…OK
cmk | 2026-06-08T14:35:44.669689277Z Starting nagios…OK
cmk | 2026-06-08T14:35:44.744701857Z Starting apache…OK
cmk | 2026-06-08T14:35:45.214570016Z Starting crontab…OK
cmk exited with code 2 (restarting)
Never had this before. Ideas?
EDIT: OK I restored CheckMK from backups and then tried again. Worked second time round. Not sure what the issue was with the first attempt. Anyway - all good now thank you.
1 Like
Dirk
June 9, 2026, 2:03pm
5
People would appreciate it but are scared at the same time
@Dirk : You are right. I personally would love to see Checkmk itself switch to semantic versioning, but I can’t see it happen anytime soon.
I’d rather drop the 0 then going to Semantic Versioning for a project like Checkmk.
1 Like