Checkmk up to 2.2.0/2.3.0p48/2.4.0p34/2.5.0p9 Reports improper authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.1 | $0-$5k | 2.72 |
Summary
A vulnerability has been found in Checkmk up to 2.2.0/2.3.0p48/2.4.0p34/2.5.0p9 and classified as problematic. The impacted element is an unknown function of the component Reports. The manipulation leads to improper authorization. This vulnerability is listed as CVE-2026-15227. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Checkmk up to 2.2.0/2.3.0p48/2.4.0p34/2.5.0p9. It has been rated as problematic. This issue affects an unknown part of the component Reports. The manipulation with an unknown input leads to a improper authorization vulnerability. Using CWE to declare the problem leads to CWE-285. The product does not perform or incorrectly performs an authorization check when an actor attempts to access a resource or perform an action. Impacted is integrity. The summary by CVE is:
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.
The advisory is shared at checkmk.com. The identification of this vulnerability is CVE-2026-15227 since 07/09/2026. The exploitation is known to be easy. The attack may be initiated remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1548.002 for this issue.
Upgrading to version 2.3.0p49, 2.4.0p35 or 2.5.0p10 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-51529). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 4.3VulDB Meta Temp Score: 4.1
VulDB Base Score: 4.3
VulDB Temp Score: 4.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Improper authorizationCWE: CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Checkmk 2.3.0p49/2.4.0p35/2.5.0p10
Timeline
07/09/2026 CVE reserved07/31/2026 Advisory disclosed
07/31/2026 VulDB entry created
07/31/2026 VulDB entry last update
Sources
Advisory: checkmk.comStatus: Confirmed
CVE: CVE-2026-15227 (🔒)
GCVE (CVE): GCVE-0-2026-15227
GCVE (VulDB): GCVE-100-385073
EUVD: 🔒
Entry
Created: 07/31/2026 14:54Updated: 07/31/2026 18:50
Changes: 07/31/2026 14:54 (53), 07/31/2026 18:50 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.