Search for packages
| purl | pkg:deb/debian/python-pip@26.0.1%2Bdfsg-1?distro=trixie |
| Vulnerability | Summary | Fixed by |
|---|---|---|
| This package is not known to be affected by vulnerabilities. | ||
| Vulnerability | Summary | Aliases |
|---|---|---|
| VCID-75s4-h132-6fe1 | 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-2021-3572
GHSA-5xp3-jfq3-5q8x PYSEC-2021-437 |
| VCID-86pc-jqve-wyg7 | 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-2014-8991
GHSA-53mr-44pp-crf4 PYSEC-2014-11 |
| VCID-ecex-5hqz-9bbd | pip's fallback tar extraction doesn't check symbolic links point to extraction directory 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 vulnerabilities that are remediated by using a Python version that implements PEP 706. Note that this is a vulnerability in pip's fallback implementation of tar extraction for Python versions that don't implement PEP 706 and therefore are not secure to all vulnerabilities in the Python 'tarfile' module. If you're using a Python version that implements PEP 706 then pip doesn't use the "vulnerable" fallback code. Mitigations include upgrading to a version of pip that includes the fix, upgrading to a Python version that implements PEP 706 (Python >=3.9.17, >=3.10.12, >=3.11.4, or >=3.12), applying the linked patch, or inspecting source distributions (sdists) before installation as is already a best-practice. |
CVE-2025-8869
GHSA-4xh5-x5gv-qwph |
| VCID-etur-1aaz-9uf3 | pip Path Traversal vulnerability 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 overwrite executable files in typical situations. |
CVE-2026-1703
GHSA-6vgw-5pg2-w6jp |
| VCID-ezkx-6k4g-n3az | 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-1629
GHSA-g3p5-fjj9-h8gj PYSEC-2013-8 |
| VCID-g6gg-vgks-xyeb | 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. |
CVE-2023-5752
GHSA-mq26-g339-26xf PYSEC-2023-228 |
| VCID-u8br-mhnn-vyas | 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-1888
GHSA-4gv5-qhvr-36vv PYSEC-2013-9 |
| VCID-vrnn-n6vw-gygb | 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-2019-20916
GHSA-gpvv-69j7-gwj8 PYSEC-2020-173 |
| VCID-wsyq-cpss-nbcq | 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-2013-5123
GHSA-c5h8-cq4v-cvfm PYSEC-2019-160 |