pip
PyPI11 known CVEs affecting this package
Aggregated from OSV, GitHub Security Advisories, NVD, and vendor advisories. Each CVE links to its full detail page with vendor advisories, patches, fixed versions, and remediation guidance.
CVEs affecting pippage 1 of 1
- CVE-2013-1629NONECVSS 0.0EG 0.0✓ Fixed in 1.32013-08-06
vulnerable: 0.2 ... 1.2.1 (24 versions)
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 execute arbitrary code via a crafted response to a "pip install"…
- CVE-2013-1888NONECVSS 0.0EG 0.0✓ Fixed in 1.32013-08-17
vulnerable: 0.2 ... 1.2.1 (24 versions)
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.
- CVE-2013-5123MEDIUMCVSS 5.9EG 5.9✓ Fixed in 1.52019-11-05
vulnerable: 0.2 ... 1.4.1 (28 versions)
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.
- CVE-2014-8991NONECVSS 0.0EG 0.0✓ Fixed in 6.02014-11-24
vulnerable: 1.3 ... 1.5.6 (11 versions)
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.
- CVE-2019-20916HIGHCVSS 7.5EG 7.5✓ Fixed in 19.22020-09-04
vulnerable: 0.2 ... 19.1.1 (76 versions)
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 demonstrated by overwriting the /root/.ssh/authorized_keys fil…
- CVE-2021-3572MEDIUMCVSS 5.7EG 5.7✓ Fixed in 21.12021-11-10
vulnerable: 0.2 ... 9.0.3 (102 versions)
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 repository. The highest threat from this vulnerability is to da…
- CVE-2023-5752MEDIUMCVSS 5.5EG 5.5✓ Fixed in 23.32023-10-25
vulnerable: 0.2 ... 9.0.3 (134 versions)
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 configuration options to the "hg clone" call (ie "--config"). Cont…
- CVE-2025-8869MEDIUMCVSS 5.9EG 0.0✓ Fixed in 25.32025-09-24
vulnerable: 0.2 ... 9.0.3 (151 versions)
When extracting a tar archive pip may not check symbolic links point into the extraction directory if the tarfile module doesn't implement PEP 706. Note that upgrading pip to a "fixed" version for this vulnerability doesn't fix all known v…
- CVE-2026-1703LOWCVSS 2.0EG 0.0✓ Fixed in 26.02026-02-02
vulnerable: 0.2 ... 9.0.3 (152 versions)
When pip is installing and extracting a maliciously crafted wheel archive, files may be extracted outside the installation directory. The path traversal is limited to prefixes of the installation directory, thus isn't able to inject or ove…
- CVE-2026-3219MEDIUMCVSS 4.6EG 4.6✓ Fixed in 26.12026-04-20
vulnerable: 0.2 ... 9.0.3 (154 versions)
pip handles concatenated tar and ZIP files as ZIP files regardless of filename or whether a file is both a tar and ZIP file. This behavior could result in confusing installation behavior, such as installing "incorrect" files according to t…
- CVE-2026-6357MEDIUMCVSS 5.3EG 5.3✓ Fixed in 26.12026-04-27
vulnerable: 0.2 ... 9.0.3 (154 versions)
pip prior to version 26.1 would run self-update check functionality after installing wheel files which required importing well-known Python modules names. These module imports were intentionally deferred to increase startup time of the pip…
Check whether pip is used in your infrastructure
EchelonGraph scans your cloud and SBOMs to map every package to your actual deployments. See blast radius for pip CVEs against the assets you own.
Start Free Scan →