Aimhubio vulnerabilities
We track 16 vulnerabilities in Aimhubio products across 2 products. 16 are rated high or critical, and none are known to be exploited. The most recent was published on September 4, 2026.
Latest Aimhubio vulnerabilities
- 9.8 Critical severity
aim: Missing Authentication for Critical Functionality
Aim 3.29.1 remote tracking server fails to authenticate requests and dispatches arbitrary methods through getattr without allowlist validation. Unauthenticated attackers can register clients, instantiate Repo resources, and invoke arbitrary methods to read exp
- 9.9 Critical severity
A vulnerability classified as critical was found in aimhubio aim up to 3.29.1.
A vulnerability classified as critical was found in aimhubio aim up to 3.29.1. This vulnerability affects the function RestrictedPythonQuery of the file /aim/storage/query.py of the component run_view Object Handler. The manipulation of the argument Abfrage le
- 7.5 High severity
aimhubio/aim: Excessive Data Query Operations in a Large Data Table
In version 3.25.0 of aimhubio/aim, a denial of service vulnerability exists. By tracking a large number of `Text` objects and then querying them simultaneously through the web API, the Aim web server becomes unresponsive to other requests for an extended perio
- 7.5 High severity
aimhubio/aim: Allocation of Resources Without Limits or Throttling
In version 3.25.0 of aimhubio/aim, the tracking server is vulnerable to a denial of service attack. The server overrides the maximum size for websocket messages, allowing very large images to be tracked. This causes the server to become unresponsive to other r
- 9.1 Critical severity
aimhubio/aim: Improper Limitation of a Pathname to a Restricted Directory
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
- 8.1 High severity
aimhubio/aim: Improper Neutralization of Special Elements Used in a Template Engine
In version 3.22.0 of aimhubio/aim, the AimQL query language uses an outdated version of the safer_getattr() function from RestrictedPython. This version does not protect against the str.format_map() method, allowing an attacker to leak server-side secrets or p
- 7.5 High severity
aimhubio/aim: Synchronous Access of Remote Resource without Timeout
In version 3.23.0 of aimhubio/aim, certain methods that request data from external servers do not have set timeouts, causing the server to wait indefinitely for a response. This can lead to a denial of service, as the tracking server does not respond to other
- 9.6 Critical severity
aimhubio/aim: Cross-Site Request Forgery
aimhubio/aim version 3.22.0 contains a Cross-Site Request Forgery (CSRF) vulnerability in the tracking server. The vulnerability is due to overly permissive CORS settings, allowing cross-origin requests from all origins. This enables CSRF attacks on all endpoi
- 7.5 High severity
aimhubio/aim: Improper Limitation of a Pathname to a Restricted Directory
In version 3.22.0 of aimhubio/aim, the LocalFileManager._cleanup function in the aim tracking server accepts a user-specified glob-pattern for deleting files. The function does not verify that the matched files are within the directory managed by LocalFileMana
- 9.1 Critical severity
aimhubio/aim: External Control of File Name or Path
A vulnerability in aimhubio/aim version 3.19.3 allows an attacker to exploit the `tarfile.extractall()` function to extract the contents of a maliciously crafted tarfile to arbitrary locations on the host server. The attacker can control `repo.path` and `run_h
- 7.5 High severity
aimhubio/aim: Allocation of Resources Without Limits or Throttling
A vulnerability in aimhubio/aim version 3.25.0 allows for a denial of service (DoS) attack. The issue arises when a large number of tracked metrics are retrieved simultaneously from the Aim web API, causing the web server to become unresponsive. The root cause
- 7.5 High severity
aimhubio/aim: Uncontrolled Resource Consumption
In version 3.23.0 of aimhubio/aim, the ScheduledStatusReporter object can be instantiated to run on the main thread of the tracking server, leading to the main thread being blocked indefinitely. This results in a denial of service as the tracking server become
- 9.8 Critical severity
aimhubio/aim: Path Traversal: '..filename'
A vulnerability in the `_backup_run` function in aimhubio/aim version 3.19.3 allows remote attackers to overwrite any file on the host server and exfiltrate arbitrary data. The vulnerability arises due to improper handling of the `run_hash` and `repo.path` par
- 7.5 High severity
aimhubio/aim: Loop with Unreachable Exit Condition
A vulnerability in aimhubio/aim version 3.19.3 allows an attacker to cause an infinite loop by configuring the remote tracking server to point at itself. This results in the server endlessly connecting to itself, rendering it unable to respond to other connect
- 8.8 High severity
aimhubio/aim: Cross-Site Request Forgery
aimhubio/aim is vulnerable to Cross-Site Request Forgery (CSRF), allowing attackers to perform actions such as deleting runs, updating data, and stealing data like log records and notes without the user's consent. The vulnerability stems from the lack of CSRF
- 9.8 Critical severity
aimhubio/aim: Improper Control of Generation of Code
A critical Remote Code Execution (RCE) vulnerability was identified in the aimhubio/aim project, specifically within the `/api/runs/search/run/` endpoint, affecting versions >= 3.0.0. The vulnerability resides in the `run_search_api` function of the `aim/web/a