Aimstack's vulnerability footprint concentrates in its AIM product, a narrowly scoped offering that nonetheless ranks among the more prominent vendors in the vulnerability landscape. Vulnerabilities affecting this vendor skew strongly toward critical-severity outcomes, reflecting the product's role in handling sensitive data and administrative functions where input validation and resource-management failures carry outsized consequences. The exposure recurs through weakness classes including path traversal, cross-site scripting, resource-exhaustion conditions, cross-site request forgery, and remote-resource access without timeout—a pattern characteristic of web-facing administrative tools where parser robustness, input sanitization, and rate-limiting are essential controls. Defenders should treat Aimstack advisories as high-priority, particularly those affecting internet-reachable instances; current exploitation activity and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Aimstack over time
Signals from CVEs in this vendor scope (23 CVEs).
23 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2024-6396CRITICAL 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 vul | Jul 12, 2024 | 9.8 | 68 | NO | YES |
CVE-2024-2195CRITICAL 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 | Apr 10, 2024 | 9.8 | 30 | NO | NO |
CVE-2021-43775HIGH Aim is an open-source, self-hosted machine learning experiment tracking tool. Versions of Aim prior to 3.1.0 are vulnerable to a path traversal attack. By manipulating variables th | Nov 23, 2021 | 8.6 | 28 | NO | NO |
CVE-2025-5321CRITICAL 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 th | May 29, 2025 | 9.9 | 27 | NO | NO |
CVE-2024-7760CRITICAL 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 | Mar 20, 2025 | 9.6 | 25 | NO | NO |
CVE-2025-51464HIGH 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/report | Jul 22, 2025 | 8.8 | 24 | NO | NO |
CVE-2024-8769CRITICAL 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` para | Mar 20, 2025 | 9.1 | 24 | NO | NO |
CVE-2024-6829CRITICAL 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 arbitra | Mar 20, 2025 | 9.1 | 24 | NO | NO |
CVE-2024-8238HIGH 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 th | Mar 20, 2025 | 8.1 | 22 | NO | NO |
CVE-2024-2196HIGH 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 | Apr 10, 2024 | 8.8 | 22 | NO | NO |
Signals from CVEs in this vendor scope (23 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Aimstack.
Media articles that mention a CVE ID that affects a product developed by Aimstack — matched by CVE ID, not by vendor name.