# CVE-2024-8238: Unrestricted Code Execution in aimhubio/aim

> Attackers can achieve unrestricted code execution or leak secrets via AimQL queries exploiting unsafe str.format_map() usage in Aim.

- **Severity:** Medium 5.9 (`CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Mar 2025
- **Updated:** 15 Oct 2025
- **Also known as:** GHSA-r229-5wgf-f28g, PYSEC-2026-1094

## What is CVE-2024-8238?

CVE-2024-8238 is a medium-severity code injection vulnerability in aimhubio/aim, published on 20 Mar 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 potentially gain unrestricted code execution. The vulnerability arises because str.format_map() can read arbitrary attributes of Python objects, enabling attackers to access sensitive variables such as os.environ. If an attacker can write files to a known location on the Aim server, they can use str.format_map() to load a malicious .dll/.so file into the Python interpreter, leading to unrestricted code execution.

Weakness: CWE-1336 (Improper Neutralization of Special Elements Used in a Template Engine)

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

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.22.0 | None |
| `aim` | PyPI | From 3.0.0 to 3.22.0 | None |
| `aim` | PyPI | From 3.0.0 to 3.22.0 | None |

Products: Aimstack Aim.

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

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

## Is CVE-2024-8238 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-8238 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-2195](https://insights.sbomify.com/CVE-2024-2195/): Remote Code Execution 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)

## Fix prompt for AI coding agents

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

What it is: CVE-2024-8238 is a medium-severity code injection vulnerability in aimhubio/aim, published on 20 Mar 2025. 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-8238 exists.

Affected packages and fixed versions:
- aim (PyPI): affected from 3.0.0 up to 3.22.0; no fix listed
- aim (PyPI): affected from 3.0.0 up to 3.22.0; no fix listed
- aim (PyPI): affected from 3.0.0 up to 3.22.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-8238/ (Markdown: https://insights.sbomify.com/CVE-2024-8238/index.md)
```

## Sources

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

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