Checkmk up to 2.1.0/2.2.0p45/2.3.0p37/2.4.0p12 Report Scheduler path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 5.8 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Checkmk up to 2.1.0/2.2.0p45/2.3.0p37/2.4.0p12. This affects an unknown function of the component Report Scheduler. Performing a manipulation results in path traversal. This vulnerability was named CVE-2025-39664. The attack may be initiated remotely. There is no available exploit. It is recommended to upgrade the affected component.
Details
A vulnerability classified as critical has been found in Checkmk up to 2.1.0/2.2.0p45/2.3.0p37/2.4.0p12. This affects some unknown processing of the component Report Scheduler. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. This is going to have an impact on integrity, and availability. The summary by CVE is:
Insufficient escaping in the report scheduler within Checkmk <2.4.0p13, <2.3.0p38, <2.2.0p46 and 2.1.0 (EOL) allows authenticated attackers to define the storage location of report file pairs beyond their intended root directory.
The advisory is shared at checkmk.com. This vulnerability is uniquely identified as CVE-2025-39664 since 04/16/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available. MITRE ATT&CK project uses the attack technique T1006 for this issue.
Upgrading to version 2.2.0p46, 2.3.0p38 or 2.4.0p13 eliminates this vulnerability.
The vulnerability is also documented in the vulnerability database at CERT Bund (WID-SEC-2025-2253). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Affected
- Checkmk Checkmk
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 5.9VulDB Meta Temp Score: 5.8
VulDB Base Score: 5.4
VulDB Temp Score: 5.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔒
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: Path traversalCWE: CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
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.2.0p46/2.3.0p38/2.4.0p13
Timeline
04/16/2025 CVE reserved10/09/2025 Advisory disclosed
10/09/2025 VulDB entry created
12/05/2025 VulDB entry last update
Sources
Advisory: checkmk.comStatus: Confirmed
CVE: CVE-2025-39664 (🔒)
GCVE (CVE): GCVE-0-2025-39664
GCVE (VulDB): GCVE-100-327753
CERT Bund: WID-SEC-2025-2253 - Checkmk: Mehrere Schwachstellen
Entry
Created: 10/09/2025 18:44Updated: 12/05/2025 12:27
Changes: 10/09/2025 18:44 (66), 10/10/2025 23:22 (7), 12/05/2025 12:27 (11)
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.