p PatchFirst

PatchFirst · Latest vulnerabilities

pip vulnerabilities

Vulnerabilities published for pip in the last 30 days: 0. Listed in the KEV catalogue: 0.

Filter vulnerabilities
Clear filters

Vulnerabilities: 13

  1. CVE-2026-13346

    Medium · CVSS 5.6EPSS 0.29%Fix available

    pip absolute path traversal during download from malicious package indexes

    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.

    • Update to 26.2
    • Update to 26.2.0
    Published Updated
  2. CVE-2026-8643

    Medium · CVSS 4.1EPSS 0.47%Fix available

    pip can extract console_scripts and gui_scripts outside installation directory

    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.

    • Update to 26.1.2
    Published Updated
  3. CVE-2026-6357

    Medium · CVSS 5.3EPSS 0.17%Fix available

    pip self-update functionality can import newly installed modules after wheel installation

    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 CLI. The patch changes self-update functionality to run before wheels are installed to prevent newly-installed modules from being imported shortly after the installation of a wheel package. Users should still review package contents prior to installation.

    • Update to 26.1
    Published Updated
  4. CVE-2026-3219

    Medium · CVSS 4.6EPSS 0.14%Fix available

    pip doesn't reject concatenated ZIP and tar archives

    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 the filename of the archive. New behavior only proceeds with installation if the file identifies uniquely as a ZIP or tar archive, not as both.

    • Update to 26.1
    Published Updated
  5. CVE-2026-1703

    Low · CVSS 2EPSS 0.44%Fix available

    Limited path traversal when installing wheel archives

    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.

    • Update to 26.0
    Published Updated
  6. CVE-2025-8869

    Medium · CVSS 5.9EPSS 0.47%Fix available

    Fallback tar extraction in pip 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 co

    • Update to 25.3
    Published Updated
  7. CVE-2023-5752

    Medium · CVSS 5.5EPSS 0.5%Fix available

    Mercurial configuration injectable in repo revision when installing via pip

    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.

    • Update to 23.3
    Published Updated
  8. CVE-2021-3572

    Medium · CVSS 5.7EPSS 1.83%Fix available

    CVE-2021-3572

    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.

    • Update to 21.1
    Published Updated
  9. CVE-2019-20916

    High · CVSS 7.5EPSS 3%Fix available

    CVE-2019-20916

    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.

    • Update to 19.2
    Published Updated
  10. CVE-2013-1629

    High · CVSS 8.4EPSS 6.19%Fix available

    CVE-2013-1629

    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.

    • Update to 1.3
    Published Updated

Check your server

Check your installed stack and versions against the current vulnerability feeds.

Check your server →