← Back
CVE-2025-8917
Path Traversal in clearml (CVE-2025-8917)
Summary
path traversal in clearml (CVE-2025-8917). Confidential information can be exposed externally. Exploitable via ``safe_extract``. Mitigation: upgrade to `2.0.2` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2025-8917** has been found in clearml.
Attackers can target a specific entry point like ``safe_extract`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade clearml to **2.0.2** or later.
If unsure, ask your IT team or search "clearml CVE-2025-8917" on the vendor's site.
CVE-2025-8917 (clearml) — CWE-22 /
Attack vector: local
Attack surface: `safe_extract`
Patched: `2.0.2` — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
❓ What is the problem
**Path traversal** (CWE-22) exists in clearml. Attackers reach the vulnerable code path via ``safe_extract`` without authentication.
📍 Affected scope
clearml — . Attack surface: `safe_extract`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **2.0.2**.
🛡️ Workaround
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
🔍 Detection
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run `grep -r 'clearml' .` against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response Actions (7 steps)
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'clearml' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で `clearml` を grep し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade clearml to 2.0.2ステージング環境で 2.0.2 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
PyPI
clearml
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"2.0.2"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2025-8917
- advisory https://github.com/advisories/GHSA-579p-qf78-fqm2
- package https://github.com/clearml/clearml
- package https://pypi.org/project/clearml
- web https://github.com/clearml/clearml/commit/64fb2bcbdbb87a74af90dd723d5ef4a99fceeb73
- web https://huntr.com/bounties/588fcdd1-fea4-4cc2-a9f8-851701dcb576