CVE-2026-24095
Improper Permission Enforcement in Checkmk Enables Unauthorized Actions
Publication date: 2026-02-09
Last updated on: 2026-02-09
Assigner: Checkmk GmbH
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| checkmk | checkmk | to 2.4.0p21 (exc) |
| checkmk | checkmk | to 2.3.0p43 (exc) |
| checkmk | checkmk | 2.2.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-862 | The product does not perform an authorization check when an actor attempts to access a resource or perform an action. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is an improper permission enforcement issue in certain versions of Checkmk (2.4.0 before 2.4.0p21, 2.3.0 before 2.3.0p43, and 2.2.0 which is end-of-life). It allows users who have the "Use WATO" permission to access the "Analyze configuration" page by directly navigating to its URL, bypassing the intended permission check for "Access analyze configuration."
Furthermore, if these users also have the "Make changes, perform actions" permission, they can perform unauthorized actions such as disabling checks or acknowledging results.
How can this vulnerability impact me? :
This vulnerability can impact you by allowing users with limited permissions to access and perform actions they are not authorized to do. Specifically, users with the "Use WATO" permission can bypass restrictions to access sensitive configuration analysis pages.
If these users also have the "Make changes, perform actions" permission, they could disable monitoring checks or acknowledge results without proper authorization, potentially leading to incorrect monitoring data, missed alerts, or unauthorized changes in the system.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know