CVE-2020-15801

CRITICALNVD 9.89.8—

9.8

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

CVSS v3: 9.8
EG Score: 9.8(medium)
EPSS: 70.3%
KEV: Not listed

Published

July 17, 2020

Last Modified

November 21, 2024

References (6)

cve@mitrehttps://bugs.python.org/issue41304
cve@mitrehttps://github.com/python/cpython/pull/21495
cve@mitrehttps://security.netapp.com/advisory/ntap-20200731-0003/
af854a3a-2127-422b-91ae-364da2661108https://bugs.python.org/issue41304
af854a3a-2127-422b-91ae-364da2661108https://github.com/python/cpython/pull/21495
af854a3a-2127-422b-91ae-364da2661108https://security.netapp.com/advisory/ntap-20200731-0003/

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 20× in last 30d)

Every time one of our enrichment pipelines (NVD, MITRE cvelistV5, EPSS, CISA KEV, GHSA, OSV, vendor advisories) ran against this CVE. Most recent first.

2026-06-02 20:11 UTCepss_batch
2026-06-02 20:11 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-06-01 13:50 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 22:29 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-31 00:15 UTCepss_batch
2026-05-29 13:42 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-28 13:43 UTCepss_batch
2026-05-27 13:39 UTCepss_batch
2026-05-27 01:01 UTCEG score recompute
2026-05-27 01:01 UTCGHSA enrichment
2026-05-26 13:42 UTCepss_batch
2026-05-26 13:42 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-26 07:17 UTCepss_batch
2026-05-25 13:16 UTCOSV refresh
2026-05-24 16:48 UTCepss_batch

Frequently asked(5)

What is CVE-2020-15801?

CVE-2020-15801 is a critical vulnerability published on July 17, 2020. 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.

When was CVE-2020-15801 disclosed?

CVE-2020-15801 was first published in the National Vulnerability Database on July 17, 2020, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.

Is CVE-2020-15801 actively exploited?

CVE-2020-15801 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 70.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.

What is the CVSS score of CVE-2020-15801?

CVE-2020-15801 has a CVSS v3 base score of 9.8 (NVD).

How do I remediate CVE-2020-15801?

Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2020-15801, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2020-15801

Explore →

Is Your Infrastructure Affected by CVE-2020-15801?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs

CVE-2020-15801

📅 Published

🔄 Last Modified

🔗 References (6)

Weakness Classification(2)

Data Freshness Timeline

❓ Frequently asked(5)

Dependency Blast Radius

Is Your Infrastructure Affected by CVE-2020-15801?

🔗 Related CVEs(same CWE)

Same CWE

Published

Last Modified

References (6)

Frequently asked(5)

Related CVEs(same CWE)