Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain low-privilege Checkmk account
-
DeliveryIdentify target report owned by another user
-
ExploitSubmit report modification request without required permission
-
ExecutionServer skips authorization check
-
ImpactOverwrite victim user's report content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V8 - Authorization Authorization checks on every request
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a valid authenticated Checkmk session with at minimum a low-privilege account (PR:L confirmed by CVSS 4.0 vector). The attacker must not hold the 'Edit foreign Reports' permission - that is precisely the condition that should block the action but fails to do so. No special configuration, no non-default feature, and no specific platform variant is required beyond having access to a vulnerable Checkmk instance and knowledge of another user's report identifier. Exploitation is limited to integrity impact on reports; the flaw does not provide access to credentials, host data, or monitoring infrastructure configuration. Users without any valid Checkmk account cannot exploit this remotely. |
| Impact | The CVSS 4.0 score of 5.3 (Medium) is consistent with the actual risk profile. The vector confirms network reachability (AV:N) and low complexity (AC:L), but impact is strictly limited to low integrity on the vulnerable system (VI:L) with no confidentiality or availability consequence (VC:N/VA:N). No scope change affects downstream systems (SC:N/SI:N/SA:N). No CISA KEV listing exists, no public exploit or POC has been identified, and EPSS data is not provided - suggesting this has not attracted opportunistic attacker attention. The primary real-world concern is in multi-user or multi-team Checkmk deployments where report isolation between users is relied upon for data governance or operational separation. A single malicious or compromised low-privilege account could silently corrupt monitoring reports for other teams. The EOL status of version 2.2.0 means those users receive no patch and must upgrade. |
| Exploit ScenarioDerived | An authenticated Checkmk user with a standard low-privilege account - one explicitly not granted the 'Edit foreign Reports' permission - navigates to or directly submits a crafted request to the report modification endpoint, referencing a report owned by another user. Because the authorization check is absent, the server accepts and applies the modification, overwriting the target report's content or configuration without any alert to the report owner. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 31, 2026
Checkmk's reporting module fails to enforce the 'Edit foreign Reports' permission, allowing any authenticated user - regardless of their assigned role - to modify reports belonging to other users. Affected are all Checkmk deployments running versions prior to 2.5.0p10, 2.4.0p35, or 2.3.0p49, as well as the end-of-life 2.2.0 branch. No public exploit code or active exploitation has been identified at time of analysis, and real-world impact is bounded to report integrity rather than system compromise, but the permission bypass undermines multi-tenant trust boundaries in shared monitoring environments.
RemediationAI
Upgrade to Checkmk 2.5.0p10, 2.4.0p35, or 2.3.0p49 as appropriate for your branch; these are the confirmed fixed versions per the vendor's werk advisory at https://checkmk.com/werk/20003. Users on the end-of-life 2.2.0 branch must migrate to a supported release to receive the fix. As a compensating control prior to patching, administrators can restrict the Checkmk web interface to trusted network segments or authenticated VPN access, reducing the pool of users who can reach the vulnerable endpoint - though this does not eliminate the flaw for internal users. Auditing report ownership and reviewing recent report modification logs for unexpected changes is advisable on unpatched instances.
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 (by Checkmk GmbH, CPE: cpe:2.3:a:checkmk_gmbh:checkmk:*:*:*:*:*:*:*:*) is an enterprise IT infrastructure monitoring platform. The root cause is CWE-862 (Missing Authorization): the server-side handler for modifying reports does not verify that the requesting user holds the 'Edit foreign Reports' permission before acting on reports owned by a different account. This is a classic broken access control pattern - the permission exists in the role model but is not enforced at the business-logic layer for this specific operation. The CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) confirms the flaw is reachable over the network with low complexity and requires only a valid authenticated session, with no attack-side prerequisites beyond standard HTTP access to the Checkmk web interface.
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:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N
Network-reachable via web UI, low complexity, authenticated low-privilege user required; only report integrity affected, no confidentiality or availability loss, scope unchanged.
Primary rating from Vendor (Checkmk).
CVSS VectorVendor: Checkmk
Lifecycle Timeline
1DescriptionCVE.org
Missing authorization in Checkmk <2.5.0p10, <2.4.0p35, <2.3.0p49, and 2.2.0 (EOL) allows an authenticated user lacking the "Edit foreign Reports" permission to modify reports owned by other users.
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
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
Check_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
Local privilege escalation in Checkmk allows site users with high privileges to escalate to root by manipulating site co
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
EUVD-2026-51529
GHSA-m93w-q9x6-3m46
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB