# CVE-2024-2195: Remote Code Execution in aimhubio/aim

> Attackers can execute arbitrary code on the server via the run search API endpoint in Aim, leading to full system compromise.

- **Severity:** Critical 9.8 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-mxvw-cj37-8g2h, PYSEC-2026-260

## What is CVE-2024-2195?

CVE-2024-2195 is a critical code injection vulnerability in aimhubio/aim, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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/api/runs/views.py` file, where improper restriction of user access to the `RunView` object allows for the execution of arbitrary code via the `query` parameter. This issue enables attackers to execute arbitrary commands on the server, potentially leading to full system compromise.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2024-2195?

3 open source packages ship an affected version, including aim. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aim` | PyPI | From 3.0.0 to 3.25.0 | None |
| `aim` | PyPI | From 3.0.0 to 3.25.0 | None |
| `aim` | PyPI | From 3.0.0 to 3.25.0 | None |

Products: Aimstack Aim.

## How do I fix CVE-2024-2195?

No fix has been published for CVE-2024-2195 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-2195 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2195 exists.

## Other vulnerabilities in aimhubio/aim

- [CVE-2024-6396](https://insights.sbomify.com/CVE-2024-6396/): Arbitrary File Overwrite and Data Exfiltration in aimhubio/aim (critical 9.8)
- [CVE-2024-6829](https://insights.sbomify.com/CVE-2024-6829/): Arbitrary File Overwrite through tarfile-extraction in aimhubio/aim (critical 9.1)
- [CVE-2024-8769](https://insights.sbomify.com/CVE-2024-8769/): Arbitrary File Deletion via Relative Path Traversal in aimhubio/aim (critical 9.1)
- [CVE-2025-51464](https://insights.sbomify.com/CVE-2025-51464/): Aim vulnerable to Cross-site Scripting (high 8.8)
- [CVE-2024-2196](https://insights.sbomify.com/CVE-2024-2196/): CSRF Vulnerability in aimhubio/aim (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-2195 and fix it if it is affected.

What it is: CVE-2024-2195 is a critical code injection vulnerability in aimhubio/aim, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2195 exists.

Affected packages and fixed versions:
- aim (PyPI): affected from 3.0.0 up to 3.25.0; no fix listed
- aim (PyPI): affected from 3.0.0 up to 3.25.0; no fix listed
- aim (PyPI): affected from 3.0.0 up to 3.25.0; no fix listed

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-2195/ (Markdown: https://insights.sbomify.com/CVE-2024-2195/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-2195
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-2195
- OSV: https://osv.dev/vulnerability/CVE-2024-2195

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-2195/
Summaries are generated and may contain mistakes; the official description above is the record.