This is an announcement for an upcoming security release of Checkmk.
On Tuesday, April 7th, we will publish a patch release for all currently supported versions of Checkmk: 2.3.0 (2.3.0p46) and 2.4.0 (2.4.0p25). A patch for the 2.5.0 beta will follow the next day.
The patch contains fixes for three vulnerabilities: one with critical severity (CVE-2025-39666), one with high severity (CVE-2026-3466), and one with medium severity (CVE-2026-24096).
All editions and all configurations of Checkmk are affected.
To prepare for the patch, we recommend that all users update their environment to current patch releases (2.3.0p45 / 2.4.0p24) well in advance to reduce the risk of other, unrelated changes breaking any functionality during a security patch.
If you have any questions, please feel free to reach out to security@checkmk.com.
Hello. When is the anticipated release for 2.3.0p46? I have a patching window for a client on 2.3 tomorrow to patch OS vulnerabilities and they asked if we could roll this in to the maintenance window.
Thanks!
Yes, the werk is included in 2.4.0p25. The werks listed in the release announcement posts are correct.
The werks list is lagging behind a bit and might be showing wrong versions due to the special release process for this. Should be fixed by the end of the day.
We’re working on an update for Python in the Windows agent, but I cannot give you an ETA unfortunately.
I just want to point out for completeness sake that all CVEs in your screenshot are OpenSSL CVEs, so this is unrelated to the Python version on the server side. Here we ship OpenSSL directly. 2.4.0 ships OpenSSL 3.0.19, the beta ships 3.5.4 (and should be updated too, but like I said, unrelated to the Python version).
The checkmk server itself is not our concern currently. Every windows server that is in checkmk monitoring has a finding regarding openssl (from python from checkmk) and that are many. So there are a lot of people asking me to fix this problem including it-security for some longer time. Because of the delay there are some people who demand to look for another solution…becoming more and more.
Since python for windows has this fix included all is in your hands.