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. The <executable-name>._pth file (e.g., the python._pth file) is not affected.

Published: 2020-07-17 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2020-15801 is rated High Risk (71.8/100): CVSS Critical severity, with medium exploitation likelihood (EPSS 3.10%). EPSS rose +2.49% over the last day, indicating growing attacker interest. High exploitation likelihood—assess exposure and prioritize remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2020-15801

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.62% 3.10% +2.49%
2 2025-12-28 0.50% 0.62% +0.11%
3 2025-12-27 — 0.50% —

Full EPSS history (16 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2020-15801

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
9.8 3.1 CRITICAL
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 3.9 5.9 [email protected]
7.5 2.0 HIGH
AV:N/AC:L/Au:N/C:P/I:P/A:P Click to expand
Access vector (AV:N)
Can be exploited remotely over network reachability.
Access complexity (AC:L)
Exploitation conditions are straightforward and predictable.
Authentication (AU:N)
No authentication is required.
Confidentiality impact (C:P)
Partial confidentiality impact.
Integrity impact (I:P)
Partial integrity impact.
Availability impact (A:P)
Partial availability impact.
 10.0 6.4 [email protected]

Weakness enumeration for CVE-2020-15801

OS Trackers for CVE-2020-15801

vendor priority summary link
debian unimportant CVE-2020-15801 unimportant priority: Debian including 2 source packages (python2.7, python3.9), 2 status rows across 1 suites (bullseye): resolved 2. https://security-tracker.debian.org/tracker/CVE-2020-15801
redhat high — https://access.redhat.com/security/cve/CVE-2020-15801
ubuntu medium CVE-2020-15801 medium priority: Ubuntu including 7 source packages (python2.7, python3.4, …), 35 status rows across 5 suites (bionic, focal, trusty, upstream, xenial): not-affected 19, DNE 16. https://ubuntu.com/security/CVE-2020-15801

Affected software / configurations for CVE-2020-15801

Vendor Product Version Raw CPE
python python >= 3.7.0, < 3.7.9 cpe:2.3:a:python:python:*:*:*:*:*:*:*:*
python python >= 3.8.0, < 3.8.5 cpe:2.3:a:python:python:*:*:*:*:*:*:*:*
netapp max_data — cpe:2.3:a:netapp:max_data:-:*:*:*:*:*:*:*

References for CVE-2020-15801

URL Tags
https://bugs.python.org/issue41304 Issue Tracking Patch Vendor Advisory
https://github.com/python/cpython/pull/21495 Patch Vendor Advisory
https://security.netapp.com/advisory/ntap-20200731-0003/ Third Party Advisory
cvelogic Threat Intelligence