Pypa Pip vulnerabilities
9 vulnerabilities
Known vulnerabilities in Pypa Pip, newest first, with CVSS severity, EPSS, KEV listings, ransomware use and the affected versions.
CVE-2013-1629debianpython-pip+4
EPSS score6.19%
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" operation.CVE-2013-1888fedoraprojectfedora+2EPSS score0.36%
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-5123debianpython-pip+10EPSS score7.99%
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-2021-3572debianpython-pip+52EPSS score1.83%
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 data integrity. This is fixed in python-pip version 21.1.CVE-2014-8991debianpython-pip+5EPSS score0.39%
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-20916debianpython-pip+217EPSS score3.00%
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 file. This occurs in _download_http_url in _internal/download.py.CVE-2026-13346chainguardbazel-module-rules_python-1.6.0+60EPSS score0.29%
pip would incorrectly handle doubly-encoded package URLs from indexes allowing for files to be installed to arbitrary locations on disk even when installing wheels.
This vulnerability requires downloading or installing a package from a malicious package index to succeed, malicious packages alone are not able to exploit this vulnerability. Note that this vulnerability only materially impacts users running `pip download` with the `--only-binary` option as installing source distributions from an untrusted index is already an unsafe operation that executes code during install time.CVE-2026-8643chainguardbazel-module-rules_python-1.6.0+30EPSS score0.47%
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 being installed outside the installation directory.CVE-2023-5752chainguardgraalvm-24-graalpy+19EPSS score0.50%
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"). Controlling the Mercurial configuration can modify
how and which repository is installed. This vulnerability does not
affect users who aren't installing from Mercurial.