# CVE-2021-43775: Arbitrary file reading vulnerability in Aim

> Attackers can read arbitrary files on the server via path traversal in Aim, exposing source code and system files.

- **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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:** Yes
- **Published:** 23 Nov 2021
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8phj-f9w2-cjcc, PYSEC-2021-839

## What is CVE-2021-43775?

CVE-2021-43775 is a high-severity path traversal vulnerability in aimhubio aim, published on 23 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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 that reference files with “dot-dot-slash (../)” sequences and its variations or by using absolute file paths, it may be possible to access arbitrary files and directories stored on file system including application source code or configuration and critical system files. The vulnerability issue is resolved in Aim v3.1.0.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2021-43775?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `aim` | PyPI | All versions | 3.1.0 |
| `aim` | PyPI | All versions | 3.1.0 |
| `aim` | PyPI | All versions | 3.1.0 |

Products: Aimstack Aim.

## How do I fix CVE-2021-43775?

Upgrade aim to 3.1.0 or later.

## Is CVE-2021-43775 being exploited?

There is no known exploitation of CVE-2021-43775 in the wild and no public exploit code.

## 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-2021-43775 and fix it if it is affected.

What it is: CVE-2021-43775 is a high-severity path traversal vulnerability in aimhubio aim, published on 23 Nov 2021. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2021-43775 in the wild and no public exploit code.

Affected packages and fixed versions:
- aim (PyPI): affected all versions; fixed in 3.1.0
- aim (PyPI): affected all versions; fixed in 3.1.0
- aim (PyPI): affected all versions; fixed in 3.1.0

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-2021-43775/ (Markdown: https://insights.sbomify.com/CVE-2021-43775/index.md)
```

## Sources

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

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