Aimstack vulnerabilities
We track 12 vulnerabilities in Aimstack products. 12 are rated high or critical, and none are known to be exploited. The most recent was published on July 22, 2025.
Latest Aimstack vulnerabilities
- 8.8 High severity
Aim: Improper Neutralization of Input During Web Page Generation
Cross-site Scripting (XSS) in aimhubio Aim 3.28.0 allows remote attackers to execute arbitrary JavaScript in victims browsers via malicious Python code submitted to the /api/reports endpoint, which is interpreted and executed by Pyodide when the report is view
- 7.0 High severity
Aim: Improper Limitation of a Pathname to a Restricted Directory
Path Traversal in restore_run_backup() in AIM 3.28.0 allows remote attackers to write arbitrary files to the server's filesystem via a crafted backup tar file submitted to the run_instruction API, which is extracted without path validation during restoration.
- 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