CVE-2025-65000
CVE-2025-65000 is a medium-severity vulnerability in Checkmk with a CVSS 3.x base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-212.
Key facts
- Severity: Medium (CVSS 3.x base score 5.3)
- CVSS v4: 2.3
- EPSS exploit prediction: 0% (8th percentile)
- Actively exploited: Not listed in CISA KEV
- EU (EUVD) id: EUVD-2025-204293
- Weakness: CWE-212
- Affected product: Checkmk
- Published:
- Last modified:
Description
SSH private keys of the "Remote alert handlers (Linux)" rule were exposed in the rule page's HTML source in Checkmk <= 2.4.0p18 and all versions of Checkmk 2.3.0. This potentially allowed unauthorized triggering of predefined alert handlers on hosts where the handler was deployed.
Frequently asked questions
- What is CVE-2025-65000?
- SSH private keys of the "Remote alert handlers (Linux)" rule were exposed in the rule page's HTML source in Checkmk <= 2.4.0p18 and all versions of Checkmk 2.3.0. This potentially allowed unauthorized triggering of predefined alert handlers on hosts where the handler was deployed.
- How severe is CVE-2025-65000?
- CVE-2025-65000 has a CVSS 3.x base score of 5.3, rated medium severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
- Is CVE-2025-65000 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (8th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2025-65000?
- CVE-2025-65000 primarily affects Checkmk. In total, 74 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
- How do I fix CVE-2025-65000?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
- Does CVE-2025-65000 have an EU (EUVD) identifier?
- Yes. CVE-2025-65000 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2025-204293.
- When was CVE-2025-65000 published?
- CVE-2025-65000 was published on 2025-12-18 and last updated on 2026-06-17.
References
Affected products (74)
- cpe:2.3:a:checkmk:checkmk:2.2.0:*:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:-:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:b1:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:b2:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:b3:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:b4:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:b5:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:b6:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p1:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p10:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p11:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p12:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p13:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p14:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p15:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p16:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p17:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p18:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p19:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p2:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p20:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p21:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p22:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p23:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p24:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p25:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p26:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p27:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p28:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p29:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p3:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p30:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p31:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p32:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p33:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p34:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p35:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p36:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p37:*:*:*:*:*:*
- cpe:2.3:a:checkmk:checkmk:2.3.0:p38:*:*:*:*:*:*
More vulnerabilities in Checkmk
- CVE-2022-46836 — Critical (CVSS 9.1): PHP code injection in watolib auth.php and hosttags.php in Tribe29's Checkmk <= 2.1.0p10, Checkmk <= 2.0.0p27, and…
- CVE-2026-24096 — High (CVSS 8.8): Insufficient permission validation on multiple REST API Quick Setup endpoints in Checkmk 2.5.0 (beta) before version…
- CVE-2025-32918 — High (CVSS 8.8): Improper neutralization of Livestatus command delimiters in autocomplete endpoint within the RestAPI of Checkmk…
- CVE-2025-1712 — High (CVSS 8.8): Argument injection in special agent configuration in Checkmk <2.4.0p1, <2.3.0p32, <2.2.0p42 and 2.1.0 allows…
- CVE-2025-32917 — High (CVSS 8.8): Privilege escalation in jar_signature agent plugin in Checkmk versions <2.4.0b7 (beta), <2.3.0p32, <2.2.0p42, and…
- CVE-2024-38865 — High (CVSS 8.8): Improper neutralization of livestatus command delimiters in a specific endpoint within RestAPI of Checkmk prior to…
Other CWE-212 vulnerabilities
- CVE-2022-2818 — Critical (CVSS 9.8): Improper Removal of Sensitive Information Before Storage or Transfer in GitHub repository cockpit-hq/cockpit prior to…
- CVE-2020-11684 — Critical (CVSS 9.1): AT91bootstrap before 3.9.2 does not properly wipe encryption and authentication keys from memory before passing control…
- CVE-2026-39937 — High (CVSS 8.8): Improper removal of sensitive information before storage or transfer vulnerability in The Wikimedia Foundation…
- CVE-2022-30617 — High (CVSS 8.8): An authenticated user with access to the Strapi admin panel can view private and sensitive data, such as email and…
- CVE-2022-0355 — High (CVSS 8.8): Improper Removal of Sensitive Information Before Storage or Transfer in NPM simple-get prior to 4.0.1.
- CVE-2021-0340 — High (CVSS 8.8): In parseNextBox of IsoInterface.java, there is a possible leak of unredacted location information due to improper input…