Security Digest · Vulnerability record
CVE-2024-8769: Aim path traversal in LockManager.release_locks
A vulnerability in the LockManager.releaselocks function in aimhubio/aim (commit bb76afe) allows for arbitrary file deletion through relative path traversal.
CVSS 9.1 Critical EPSS 0.9% · p60
Should you act?
Critical and remotely reachable
No known exploitation yet, but it is network-reachable without credentials. This signal is computed from CISA KEV, EPSS and CVSS data; it is not an editorial verdict.
- 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.
From the GitHub advisory
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.
Weakness type: CWE-22, CWE-29.
Product: aim (PyPI) · Assigned by: @huntr_ai · Published: 2025-03-20
Affected and fixed versions
| Ecosystem | Package | Vulnerable | First fixed |
|---|---|---|---|
| PyPI | aim | >= 3.15.0, <= 3.27.0 | none listed |
| Vendor | Product | Affected versions (per CVE record) |
|---|---|---|
| aimhubio | aimhubio/aim | unspecified <= latest |
Severity scores
| Scored by | CVSS | Score | Vector |
|---|---|---|---|
| @huntr_ai | 3.0 | 9.1 Critical | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
| GitHub | 3.1 | 9.1 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H |
- Attack vector: network (remotely reachable)
- Attack complexity: low
- Privileges required: none (no login)
- User interaction: none
- Scope: unchanged
CVSS measures how bad a flaw is if exploited, not how likely exploitation is. Read it next to the exploitation data below.
Exploitation and urgency
- 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.
Timeline
- — CVE record published by @huntr_ai
- — GitHub-reviewed advisory GHSA-4qcx-jx49-6qrh published (critical)
- — CVE record last updated
Sources and references
Original sources first. Version and fix details should always be confirmed against the vendor or project advisory.
Vulnerability records
- GitHub Advisory GHSA-4qcx-jx49-6qrh github.com
- CVE.org record CVE-2024-8769 cve.org
- NVD entry CVE-2024-8769 nvd.nist.gov
Other references from the CVE record and advisory
- huntr.com huntr.com
- github.com github.com