Answer in brief
CVE-2024-8769 records a Critical severity (CVSS 9.1) vulnerability in Aim path traversal in LockManager.release_locks. The current sources do not mark it as known exploited. The current feed maps aim (pip), aim (pypi). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 9.1. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps aim (pip), aim (pypi). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| aimpip | >=3.15.0,<=3.27.0 | Not reported |
| aimpypi | >=3.15.0 | Not reported |
Published upstream
Mar 20, 2025
Evidence: source:ghsa:source_dates:source-dates:recordSource modified
Oct 26, 2026
Evidence: source:ghsa:source_dates:source-dates:recordFirst seen by HOL
Oct 26, 2026
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.
Quoted source text, attributed separately from HOL analysis.