# CVE-2026-8387: Relative Path Traversal in allegroai/clearml

> Attackers can exploit relative path traversal in ClearML to write arbitrary files, potentially leading to remote code execution via dataset or artifact downloads.

- **Severity:** Low 2.4 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 1 Jul 2026
- **Updated:** 1 Jul 2026
- **Also known as:** GHSA-mhhg-pjm8-92vh

## What is CVE-2026-8387?

CVE-2026-8387 is a low-severity path traversal vulnerability in allegroai/clearml, published on 1 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

A vulnerability in allegroai/clearml versions up to and including 1.16.5 allows for relative path traversal when extracting `.zip` archives using the `ZipFile.extractall()` method in `StorageManager._extract_to_cache()`. This issue arises due to the lack of path traversal validation, enabling an attacker to write arbitrary files to the filesystem. Attack vectors include dataset downloads, artifact downloads, model downloads, and offline session imports. The vulnerability can lead to remote code execution through methods such as cron job injection, SSH key overwrite, or web shell deployment. The issue is resolved in version 2.1.6.

Weakness: CWE-23 (Relative Path Traversal)

## Which versions are affected by CVE-2026-8387?


## How do I fix CVE-2026-8387?

No fix has been published for CVE-2026-8387 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-8387 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8387 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8387 and fix it if it is affected.

What it is: CVE-2026-8387 is a low-severity path traversal vulnerability in allegroai/clearml, published on 1 Jul 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-8387 exists.

Affected product: allegroai/clearml. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8387/ (Markdown: https://insights.sbomify.com/CVE-2026-8387/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8387
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8387
- OSV: https://osv.dev/vulnerability/CVE-2026-8387

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8387/
Summaries are generated and may contain mistakes; the official description above is the record.