CVE-2025-39664
BaseFortify
Publication date: 2025-10-09
Last updated on: 2025-12-04
Assigner: Checkmk GmbH
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| checkmk | checkmk | From 2.1.0 (inc) to 2.2.0 (exc) |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.2.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.3.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
| checkmk | checkmk | 2.4.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is due to insufficient escaping in the report scheduler component of Checkmk versions prior to 2.4.0p13, 2.3.0p38, 2.2.0p46, and 2.1.0 (EOL). It allows authenticated attackers to specify the storage location of report file pairs outside their intended root directory, potentially leading to unauthorized file placement.
How can this vulnerability impact me? :
The vulnerability can allow an authenticated attacker to write report files outside the designated directory, which may lead to unauthorized file storage or overwriting of files. This could result in data integrity issues or unauthorized access to sensitive information stored on the system.