Is pip 26.1 vulnerable?

PyPI · 3 releases from 26.1.0 to 26.1.2 · latest pip is 26.3 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. pip 26.1.2, the last 26.1 release, is affected by 1 known security advisory (1 medium), including CVE-2026-13346. 1 more affects earlier 26.1.x releases. Upgrade to 26.2.0 or later to fix all of them.

Upgrade with:pip install 'pip>=26.2.0'

Is your project on an affected pip?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several Python apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting pip 26.1.2

  • MediumCVE-2026-13346GHSA-qwm4-qh6w-59xr29 Jul 2026

    pip would incorrectly handle doubly-encoded package URLs from indexes

    Affected
    <26.2.0
    Fixed in
    26.2.0

Fixed within 26.1.x, affecting earlier releases

  • MediumCVE-2026-8643GHSA-wf93-45jw-76891 Jun 2026

    pip: Path traversal in console_scripts/gui_scripts entry point names allows installing scripts outside of target directory

    Affected
    <26.1.2
    Fixed in
    26.1.2

Every pip 26.1.x release

Affected: 26.1.0 to 26.1.2. Latest pip: 26.3.

VersionKnown advisories
pip 26.1.2CVE-2026-13346
pip 26.1.1CVE-2026-13346, CVE-2026-8643
pip 26.1.0CVE-2026-13346, CVE-2026-8643

Which of your client projects are still on pip 26.1?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact pip version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other pip versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the PyPI registry. Refreshed daily.