# CVE-2024-8769: Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim

> Attackers can delete arbitrary files on the server via path traversal in the aim tracking server API.

- **Severity:** Critical 9.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-4qcx-jx49-6qrh, PYSEC-2026-258

## What is CVE-2024-8769?

CVE-2024-8769 is a critical path traversal vulnerability in aimhubio/aim, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability in the `LockManager.release_locks` function in aimhubio/aim (commit bb76afe) allows for arbitrary file deletion through relative path traversal. The `run_hash` parameter, which is user-controllable, is concatenated without normalization as part of a path used to specify file deletion. This vulnerability is exposed through the `Repo._close_run()` method, which is accessible via the tracking server instruction API. As a result, an attacker can exploit this to delete any arbitrary file on the machine running the tracking server.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2024-8769?

3 open source packages ship an affected version, including aim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aim` | PyPI | From 3.15.0 to 3.27.0 | None |
| `aim` | PyPI | From 3.15.0 to 3.27.0 | None |
| `aim` | PyPI | From 3.15.0 to 3.27.0 | None |

Products: Aimstack Aim.

## How do I fix CVE-2024-8769?

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

## Is CVE-2024-8769 being exploited?

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

## Other vulnerabilities in aimhubio/aim

- [CVE-2024-6396](https://insights.sbomify.com/CVE-2024-6396/): Arbitrary File Overwrite and Data Exfiltration in aimhubio/aim (critical 9.8)
- [CVE-2024-2195](https://insights.sbomify.com/CVE-2024-2195/): Remote Code Execution in aimhubio/aim (critical 9.8)
- [CVE-2024-6829](https://insights.sbomify.com/CVE-2024-6829/): Arbitrary File Overwrite through tarfile-extraction in aimhubio/aim (critical 9.1)
- [CVE-2025-51464](https://insights.sbomify.com/CVE-2025-51464/): Aim vulnerable to Cross-site Scripting (high 8.8)
- [CVE-2024-2196](https://insights.sbomify.com/CVE-2024-2196/): CSRF Vulnerability in aimhubio/aim (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-8769 and fix it if it is affected.

What it is: CVE-2024-8769 is a critical path traversal vulnerability in aimhubio/aim, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8769 exists.

Affected packages and fixed versions:
- aim (PyPI): affected from 3.15.0 up to 3.27.0; no fix listed
- aim (PyPI): affected from 3.15.0 up to 3.27.0; no fix listed
- aim (PyPI): affected from 3.15.0 up to 3.27.0; no fix listed

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-2024-8769/ (Markdown: https://insights.sbomify.com/CVE-2024-8769/index.md)
```

## Sources

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

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