Pip vulnerabilitiesRanked by how likely they are to be used.
Pip is made by Pypa. We track 8 published vulnerabilities in it, across 119 versions. None of them is on the list of flaws known to be exploited today. If you run Pip, keep it on a version the vendor still supports.
We keep watching the known-exploited list.
Which Pip vulnerabilities are being exploited?
This is the list that matters most: flaws criminals are using now.
None of Pip's published vulnerabilities is on the list of flaws known to be exploited today. We keep watching that list.
Which Pip flaws are most likely to be used?
Ranked by the latest exploit-likelihood forecast: the chance each flaw is used in an attack in the next 30 days. A high severity score on its own doesn't tell you that. Flaws shared by many other makers' products are left out.
- 8.0%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.
- 6.2%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 execute arbitrary code via a crafted...
- 3.0%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 demonstrated by overwriting the...
- 1.8%CVE-2021-3572Medium
A flaw was found in python-pip in the way it handled Unicode separators in git references.
- 1.8%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 private index.
- 0.5%CVE-2023-5752Medium
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...
- 0.4%
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.
- 0.4%
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.
Running Pip? We'll keep checking.
Looking flaws up one at a time doesn't scale. Tell us what you run once, and we tell you which flaws matter to you, in what order, and keep watching for new ones.
- Tell us what you runPick your software from a list, or let us work it out from your website.
- We match it to every flawOver 400,000 published flaws, checked against your list.
- Ranked by real-world riskA 0 to 100 score, led by evidence criminals are using it.
- Told as soon as we knowAn alert by email, in the app or by webhook to your own tools.
Free plan, no card needed. Nothing to install.
1 new flaw affects software Acme tracks
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.
- Matched to
- Pip on Acme's software list
- What to do
- Plan in the vendor’s update
Sent to the alert recipients Acme chose. Also in the app and to Acme's webhook.
We track 8 published vulnerabilities listed under the name Pip, across 119 versions.
None of Pip's vulnerabilities is on the list of flaws known to be exploited today.
Create a Precursor Intelligence account and track Pip. We match it against every published flaw, give each one a risk score from 0 to 100 and keep watching, so you hear about new ones as soon as we know, by email, in the app or by webhook.