Live › vulnerability › CVE-2024-8769
Go to dashboardAim's LockManager.release_locks builds a file path from a user-supplied run_hash without normalization, so relative path sequences escape the intended directory. An attacker who can reach the Aim tracking server's instruction API can delete any file the server process can remove.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-26 20:56 UTC, 0h before NVD. All times on this page are UTC.
Teams running the Aim tracking server in the affected version range, especially if it listens on a network interface other than localhost. Teams that only use the Aim Python client locally without running the tracking server are not exposed through this path.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| aim | pypi | >= 3.15.0, <= 3.27.0 | – |
| aimstack aim | vendor | < 3.24.0 | 3.24.0 |
pip show aim and check whether the installed version is between 3.15.0 and 3.27.0 inclusive.aim up) is reachable from untrusted networks.aim package to a version newer than 3.27.0 (fixed version not stated in the sources; check the GHSA advisory).Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
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.
This page as .md · .json · in your agent: get_signal("CVE-2024-8769")
GitHub Advisory Database, CC-BY 4.0 · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.