PYSEC-2026-258

Vulnerability from pysec - Published: 2026-06-29 11:50 - Updated: 2026-07-01 20:22
VLAI
Details

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.

Impacted products
Name purl
aim pkg:pypi/aim

{
  "affected": [
    {
      "package": {
        "ecosystem": "PyPI",
        "name": "aim",
        "purl": "pkg:pypi/aim"
      },
      "ranges": [
        {
          "events": [
            {
              "introduced": "3.15.0"
            },
            {
              "last_affected": "3.27.0"
            }
          ],
          "type": "ECOSYSTEM"
        }
      ],
      "versions": [
        "3.15.0",
        "3.15.1",
        "3.15.2",
        "3.16.0",
        "3.16.1",
        "3.16.2",
        "3.17.0",
        "3.17.1",
        "3.17.2",
        "3.17.3",
        "3.17.4",
        "3.17.5",
        "3.17.5rc1",
        "3.17.5rc2",
        "3.17.5rc3",
        "3.17.5rc4",
        "3.18.0",
        "3.18.0.dev2",
        "3.18.0.dev3",
        "3.18.0.dev4",
        "3.18.0.dev5",
        "3.18.1",
        "3.19.0",
        "3.19.1",
        "3.19.2",
        "3.19.3",
        "3.20.1",
        "3.21.0",
        "3.22.0",
        "3.23.0",
        "3.24.0",
        "3.25.0",
        "3.25.1",
        "3.26.0.dev1",
        "3.26.1",
        "3.27.0"
      ]
    }
  ],
  "aliases": [
    "CVE-2024-8769",
    "GHSA-4qcx-jx49-6qrh"
  ],
  "details": "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.",
  "id": "PYSEC-2026-258",
  "modified": "2026-07-01T20:22:47.672031Z",
  "published": "2026-06-29T11:50:34.376380Z",
  "references": [
    {
      "type": "ADVISORY",
      "url": "https://nvd.nist.gov/vuln/detail/CVE-2024-8769"
    },
    {
      "type": "PACKAGE",
      "url": "https://github.com/aimhubio/aim"
    },
    {
      "type": "WEB",
      "url": "https://github.com/aimhubio/aim/blob/bb76afe6e9a54364f322520cc4fea2679238f904/aim/sdk/lock_manager.py#L140"
    },
    {
      "type": "WEB",
      "url": "https://huntr.com/bounties/59d3472f-f581-4beb-a090-afd36a00ecf7"
    },
    {
      "type": "PACKAGE",
      "url": "https://pypi.org/project/aim"
    },
    {
      "type": "ADVISORY",
      "url": "https://github.com/advisories/GHSA-4qcx-jx49-6qrh"
    }
  ],
  "severity": [
    {
      "score": "CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H",
      "type": "CVSS_V3"
    }
  ],
  "summary": "Aim  path traversal in LockManager.release_locks"
}



Log in or create an account to share your comment.




Tags
Taxonomy of the tags.


Loading…

Loading…

Loading…

Forecast uses a logistic model when the trend is rising, or an exponential decay model when the trend is falling. Fitted via linearized least squares.

Sightings

Author Source Type Date Other

Nomenclature

  • Seen: The vulnerability was mentioned, discussed, or observed by the user.
  • Confirmed: The vulnerability has been validated from an analyst's perspective.
  • Published Proof of Concept: A public proof of concept is available for this vulnerability.
  • Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
  • Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
  • Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
  • Not confirmed: The user expressed doubt about the validity of the vulnerability.
  • Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.

Loading…

Loading…

Loading…

Related by attack behaviour

Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.


Loading…