---
title: "CVE-2024-8769: Aim  path traversal in LockManager.release_locks"
url: https://erroneo.us/security/cve/CVE-2024-8769/
description: "CVE-2024-8769 (aim (PyPI)): A vulnerability in the LockManager.releaselocks function in aimhubio/aim (commit bb76afe) allows for arbitrary file deletion…"
type: vulnerability-record
section: "Security Digest"
date_published: 2025-03-20
date_modified: 2025-10-15
publisher: erroneo.us
author: erroneo.us Security Desk
cve: "CVE-2024-8769"
kev: false
cvss: 9.1
epss: 0.00927
license: All rights reserved. Quote with attribution and a link.
---

# CVE-2024-8769: Aim  path traversal in LockManager.release_locks

**Signal:** Critical and remotely reachable. No known exploitation yet, but it is network-reachable without credentials. (Computed from CISA KEV, EPSS and CVSS; not an editorial verdict.)

## Should you act?

- Not in CISA KEV , but CISA’s SSVC assessment records a public proof-of-concept, so attack code exists.
- EPSS 0.9% , percentile 60: FIRST’s model estimates a 0.9% chance of exploitation activity in the next 30 days, higher than 60% of all scored CVEs (moderate). EPSS is a probability, not a verdict.
- Remotely reachable with no login and no user interaction. If the vulnerable service is exposed to the internet, prioritize it.
- Only applies if your dependency tree includes aim (PyPI) >= 3.15.0, <= 3.27.0, no fixed version listed . Check your lockfile, including transitive dependencies.

## What it is

A vulnerability in the LockManager.releaselocks function in aimhubio/aim (commit bb76afe) allows for arbitrary file deletion through relative path traversal. The runhash 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.closerun() 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.

## Affected packages

- PyPI `aim` >= 3.15.0, <= 3.27.0 → fixed: none listed

## Affected products (CVE record)

- aimhubio aimhubio/aim: unspecified <= latest

## Severity

- @huntr_ai CVSS 3.0: 9.1 `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`
- GitHub CVSS 3.1: 9.1 `CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`

## Exploitation

- CISA KEV: not listed (no confirmed in-the-wild exploitation known to CISA).
- CISA SSVC assessment: exploitation poc , automatable yes , technical impact total .
- FIRST EPSS (model of 2026-10-21): 0.93% probability of exploitation activity in the next 30 days; percentile 60.

## Sources

- [GitHub Advisory GHSA-4qcx-jx49-6qrh](https://github.com/advisories/GHSA-4qcx-jx49-6qrh)
- [CVE.org record CVE-2024-8769](https://www.cve.org/CVERecord?id=CVE-2024-8769)
- [NVD entry CVE-2024-8769](https://nvd.nist.gov/vuln/detail/CVE-2024-8769)
- [huntr.com](https://huntr.com/bounties/59d3472f-f581-4beb-a090-afd36a00ecf7)
- [github.com](https://github.com/aimhubio/aim/blob/bb76afe6e9a54364f322520cc4fea2679238f904/aim/sdk/lock_manager.py#L140)

---
Source page: https://erroneo.us/security/cve/CVE-2024-8769/ · Security Digest: https://erroneo.us/security/ · More: https://erroneo.us/llms.txt