# CVE-2020-15801: In Python 3.8.4, sys.path restrictions specified in a python38._pth file are ignored, allowing code to be loaded from arbitrary locations.


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** Yes
- **Published:** 17 Jul 2020
- **Updated:** 14 Oct 2026
- **Also known as:** BIT-libpython-2020-15801, BIT-python-2020-15801, BIT-python-min-2020-15801, GHSA-45fw-qrx2-rj7m

## What is CVE-2020-15801?

CVE-2020-15801 is a critical vulnerability in Python Python, published on 17 Jul 2020. 

### Official description

In Python 3.8.4, sys.path restrictions specified in a python38._pth file are ignored, allowing code to be loaded from arbitrary locations. The <executable-name>._pth file (e.g., the python._pth file) is not affected.

Weakness: CWE-426 (Untrusted Search Path)

## Which versions are affected by CVE-2020-15801?

3 open source packages ship an affected version, including libpython, python and python-min. It affects 2 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libpython` | Bitnami | From 3.7.0 | 3.7.9, 3.8.5 |
| `python` | Bitnami | From 3.7.0 | 3.7.9, 3.8.5 |
| `python-min` | Bitnami | From 3.7.0 | 3.7.9, 3.8.5 |

Products: Netapp Max Data, Python Python.

## How do I fix CVE-2020-15801?

Upgrade libpython to a fixed version for your release line: 3.7.9 or 3.8.5.

## Is CVE-2020-15801 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-15801 and fix it if it is affected.

What it is: CVE-2020-15801 is a critical vulnerability in Python Python, published on 17 Jul 2020. 
Exploitation: There is no known exploitation of CVE-2020-15801 in the wild and no public exploit code.

Affected packages and fixed versions:
- libpython (Bitnami): affected from 3.7.0; fixed in 3.7.9, 3.8.5
- python (Bitnami): affected from 3.7.0; fixed in 3.7.9, 3.8.5
- python-min (Bitnami): affected from 3.7.0; fixed in 3.7.9, 3.8.5

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

## Sources

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

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