clearml is vulnerable to Path Traversal through its `safe_extract` function
CVE-2025-8917 · GHSA-579p-qf78-fqm2 · published 2025-10-05 · updated 2025-10-07
- Severity
- Medium
- CVSS score
- 5.8
- Chance of exploitation (EPSS)
- 0.48%
- Fixed in
- 2.0.2
- Exploitation Public proof of concept
- Automatable No
- Technical impact Total
- CISA SSVC
A vulnerability in clearml versions before 2.0.2 allows for path traversal due to improper handling of symbolic and hard links in the safe_extract function. This flaw can lead to arbitrary file writes outside the intended directory, potentially resulting in remote code execution if critical files are overwritten.
Upgrade clearml to 2.0.2 or later.
| Package | Registry | Affected | Fixed in |
|---|---|---|---|
| clearml | PyPI | < 2.0.2 | 2.0.2 |
- CriticalMCP Path Traversal Allows Full-Filesystem Read and JWT Secret Exfiltration Leading to Account Takeoverlangflow, langflow-base
- Critical@zereight/mcp-gitlab: Unauthenticated arbitrary file read via `upload_markdown` enables PAT exfiltration and full account takeover@zereight/mcp-gitlab
- CriticalFlowise RCE via SQL Database Chain Nodeflowise, flowise-components
- CriticalLangroid: SQLChatAgent dangerous-function blocklist can be bypassed with quoted or schema-qualified pg_read_file callslangroid
- Criticalfast-mcp-telegram: Bearer token path traversal bypasses reserved Telegram session protectionfast-mcp-telegram
- CriticalMCP Toolbox HTTP tool path parameters allow traversal to unintended endpointsgithub.com/googleapis/mcp-toolbox
The impact, patch and workaround text comes from the advisory, shortened (GitHub Advisory Database, CC BY 4.0). Proof-of-concept and reproduction sections and code are left out; the original advisory has them.