Advisory record · GHSA-4qcx-jx49-6qrh

Aim path traversal in LockManager.release_locks

CVSS 9.1 CriticalCriticalEPSS 0.0093 · 60th percentile

Critical, because:

  • CVSS score 9.1: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 20 Mar 2025, 12:32 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
aimPyPI>=3.15.0, <=3.27.0No fixed version yet
Identifiers
GHSA-4qcx-jx49-6qrh · CVE-2024-8769 · PYSEC-2026-258
Weakness (CWE)
CWE-22 · CWE-29
Published
20 Mar 2025
Updated
26 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

The PyPI package aim, versions 3.15.0 through 3.27.0, has a path traversal flaw in LockManager.release_locks, where a user-controllable run_hash value is concatenated into a file path without normalization. An attacker who can reach the tracking server's instruction API could use this to delete arbitrary files on the machine running the server. The source does not list a fixed version, so no upgrade target is given.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
9.1 Critical 3.0 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H CNA (@huntr_ai)
  • CISA KEV Not listed.
  • EPSS 0.0093, the 60th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:07 UTC First seen by agentprime
  2. 31 Oct 2026, 14:07 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.