Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A08:2025 - Software or Data Integrity Failures
ASVS 5.0
V13 - Configuration Search path verification
|
| Impact | The CVSS 9.3 score accurately reflects the severe technical impact-complete system compromise (VC:H/VI:H/VA:H with scope change SC:H/SI:H/SA:H)-but several factors moderate real-world risk. The attack vector is local-only (AV:L) and requires high privileges (PR:H), meaning the attacker must already possess site user credentials, which typically involves authenticated access to the Checkmk administrative interface. SSVC framework confirms exploitation is not automatable and requires specific preconditions. No public exploit code exists and no CISA KEV listing indicates active exploitation campaigns. However, low attack complexity (AC:L) means the technique is straightforward once access is obtained. This is a genuine security boundary violation requiring patching, but not an imminent mass-exploitation threat. Organizations should prioritize based on: (1) whether untrusted users have site-level access, (2) lateral movement risk if web-tier credentials are compromised, and (3) compliance requirements around privilege separation. The 2.2.0 branch is end-of-life, increasing risk for unpatched legacy installations. |
| Exploit ScenarioDerived | An attacker who has compromised credentials for a Checkmk site user-either through phishing, credential reuse, or exploitation of a separate web application vulnerability-logs into the monitoring instance with site administrative privileges. The attacker navigates to the site's file system context and creates or modifies configuration files, shell scripts, or plugin components that the 'omd' management utility will process. When a legitimate system administrator executes 'omd' commands with root privileges for routine maintenance tasks such as site updates, restarts, or configuration changes, the utility processes the attacker-controlled files without validation. This triggers execution of embedded malicious code with root privileges, granting the attacker full system control including the ability to install backdoors, access sensitive data across all monitoring instances, or pivot to monitored infrastructure using stored credentials. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Apr 07, 2026
Local privilege escalation in Checkmk allows site users with high privileges to escalate to root by manipulating site context files processed by the root-executed 'omd' administrative command. Affects Checkmk 2.2.0 (EOL), 2.3.0 before p46, 2.4.0 before p25, and 2.5.0 beta before b3. No public exploit identified at time of analysis. CVSS 9.3 reflects total technical impact, but SSVC assessment indicates non-automatable exploitation requiring existing high-privilege access, tempering the real-world urgency for organizations with strict site user access controls.
RemediationAI
Upgrade to vendor-released patched versions immediately to eliminate the privilege escalation vector. For Checkmk 2.3.0 branch, upgrade to version 2.3.0p46 or later. For Checkmk 2.4.0 branch, upgrade to version 2.4.0p25 or later. For Checkmk 2.5.0 beta users, upgrade to version 2.5.0b3 or later. Organizations running end-of-life Checkmk 2.2.0 must migrate to a supported release branch as no patch will be issued. Consult the official vendor advisory at https://checkmk.com/werk/18891 for detailed upgrade procedures and version-specific guidance. As a temporary risk reduction measure pending patching, audit and restrict site user access to only trusted administrators, implement monitoring for unexpected 'omd' command invocations, and review file integrity in site directories for unauthorized modifications. Note that workarounds do not address the root cause and patching remains the only complete remediation.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Checkmk is an infrastructure and application monitoring platform. The vulnerability stems from CWE-426 (Untrusted Search Path), where the 'omd' command-a site management utility executed with root privileges-processes files from site user-controlled directories without proper sanitization or validation. Site users in Checkmk have administrative capabilities within their monitoring instance context but operate below OS root. The flaw enables a TOCTOU-like attack where a site user can manipulate configuration files, scripts, or other resources in their site directory that 'omd' subsequently trusts when invoked by root for administrative tasks like updates or restarts. This breaks the privilege boundary between site-level and system-level administration, allowing arbitrary code execution as root through crafted file content that 'omd' processes during its execution flow.
Know when Checkmk gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:L/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Primary rating from Vendor (Checkmk) · only source for this CVE.
CVSS VectorVendor: Checkmk
Lifecycle Timeline
3DescriptionCVE.org
Local privilege escalation in Checkmk 2.2.0 (EOL), Checkmk 2.3.0 before 2.3.0p46, Checkmk 2.4.0 before 2.4.0p25, and Checkmk 2.5.0 (beta) before 2.5.0b3 allows a site user to escalate their privileges to root, by manipulating files in the site context that are processed when the omd administrative command is run by root.
Executive ViewAI
Checkmk versions 2.2.0 through 2.5.0 beta contain a local privilege escalation vulnerability that allows high-privilege site users to gain root access by manipulating administrative command processing. Organizations running affected versions must prioritize patching, particularly those with permissive site user access controls, as this directly threatens infrastructure monitoring system integrity and could enable lateral movement across monitored environments.
Apply vendor patch. If immediate patching is not feasible: restrict site user accounts to minimum required privileges (remove high-privilege role assignments where operationally possible); implement OS-level access controls limiting site user file modification permissions; enable monitoring and logging of 'omd' command execution; segregate Checkmk servers from production systems until patched.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Related Vulnerabilities in Checkmk Privilege Escalation and XSS
View all 2Check_MK before 1.2.8p26 mishandles certain errors within the failed-login save feature because of a race condition, whi
The web management console of CheckMK Raw Edition (versions 1.5.0 to 1.6.0) allows a misconfiguration of the web-app Dok
The web management console of CheckMK Enterprise Edition (versions 1.5.0 to 2.0.0p9) does not properly sanitise the uplo
Local privilege escalation in the Checkmk Windows Agent's Windows License plugin allows an authenticated low-privileged
Stored/transmitted cross-site scripting in Checkmk's distributed monitoring lets an attacker who already controls a remo
Authenticated path traversal in Checkmk's report scheduler lets a user with valid application credentials write report f
Improper restriction of excessive authentication attempts on some authentication methods in Checkmk before 2.3.0b5 (beta
The CheckMK management web console (versions 1.5.0 to 2.0.0) does not sanitise user input in various parameters of the W
Bypass of two factor authentication in RestAPI in Checkmk < 2.3.0p16 and < 2.2.0p34 allows authenticated users to bypass
Improper neutralization of active check command arguments in Checkmk < 2.1.0p32, < 2.0.0p38, < 2.2.0p4 leads to arbitrar
Improper neutralization of livestatus command delimiters in the RestAPI in Checkmk < 2.0.0p36, < 2.1.0p28, and < 2.2.0b8
Insufficient authentication flow in Checkmk before 2.2.0p18, 2.1.0p38 and 2.0.0p39 allows attacker to use locked credent
EUVD-2025-209262
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB