Pypa maintains critical Python package-management tools, most notably pip and pipenv, that are among the most widely deployed software in the Python ecosystem and sit in the supply chain of countless applications and deployments. The vendor's vulnerability profile centers on input-handling and command-execution risks inherent to package resolution and installation machinery, including improper input validation, path-traversal conditions, and command-injection weaknesses, alongside authentication and verification gaps that affect the integrity of package sourcing. Live severity, exploitation, and exposure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Pypa over time
Signals from CVEs in this vendor scope (10 CVEs).
10 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2022-21668HIGH pipenv is a Python development workflow tool. Starting with version 2018.10.9 and prior to version 2022.1.8, a flaw in pipenv's parsing of requirements files allows an attacker to | Jan 10, 2022 | 8.6 | 29 | NO | NO |
CVE-2026-8643MEDIUM pip would treat console_scripts and gui_scripts as paths instead of file names without sanitizing the resolved absolute path to the installation directory, leading to entry points | Jun 1, 2026 | 5.5 | 28 | NO | NO |
CVE-2013-5123MEDIUM The mirroring support (-M, --use-mirrors) in Python Pip before 1.5 uses insecure DNS querying and authenticity checks which allows attackers to perform man-in-the-middle attacks. | Nov 5, 2019 | 5.9 | 27 | NO | YES |
CVE-2019-20916HIGH The pip package before 19.2 for Python allows Directory Traversal when a URL is given in an install command, because a Content-Disposition header can have ../ in a filename, as dem | Sep 4, 2020 | 7.5 | 26 | NO | NO |
CVE-2018-20225HIGH An issue was discovered in pip (all versions) because it installs the version with the highest version number, even if the user had intended to obtain a private package from a priv | May 8, 2020 | 7.8 | 26 | NO | NO |
CVE-2021-3572MEDIUM A flaw was found in python-pip in the way it handled Unicode separators in git references. A remote attacker could possibly use this issue to install a different revision on a repo | Nov 10, 2021 | 5.7 | 22 | NO | NO |
CVE-2013-1629MEDIUM pip before 1.3 uses HTTP to retrieve packages from the PyPI repository, and does not perform integrity checks on package contents, which allows man-in-the-middle attackers to execu | Aug 6, 2013 | 6.8 | 20 | NO | NO |
When installing a package from a Mercurial VCS URL (ie "pip install
hg+...") with pip prior to v23.3, the specified Mercurial revision could
be used to inject arbitrary configur | Oct 25, 2023 | 3.3 | 15 | NO | NO |
pip before 1.3 allows local users to overwrite arbitrary files via a symlink attack on a file in the /tmp/pip-build temporary directory. | Aug 17, 2013 | 2.1 | 15 | NO | NO |
pip 1.3 through 1.5.6 allows local users to cause a denial of service (prevention of package installation) by creating a /tmp/pip-build-* file for another user. | Nov 24, 2014 | 2.1 | 11 | NO | NO |
Signals from CVEs in this vendor scope (10 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Pypa.
Media articles that mention a CVE ID that affects a product developed by Pypa — matched by CVE ID, not by vendor name.