Vulert records 2 vulnerabilities for pip in ghsa: 0 critical, 0 high, 2 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

How many vulnerabilities does pip have?

2 vulnerabilities are recorded for pip in the ghsa ecosystem: 0 critical, 0 high, 2 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new pip vulnerabilities disclosed?

2 vulnerabilities were recorded for pip in the last 12 months, and the oldest entry in this database dates to 20 Apr 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of pip are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor pip for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the pip version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.

Vulnerability Database · ghsa · Package report

pip: vulnerability history, versions and safety

pip is a package in the ghsa ecosystem. Vulert records 2 vulnerabilities for it across 2 affected ranges, first recorded in Apr 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

2 vulnerabilities recorded M2

1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →

2 in the last 12 months

Most recent disclosure 27 Apr 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all pip vulnerabilities

Vulert verdict on pip i

Updated on 23 Oct 2026

Careful: one of the 2 vulnerabilities Vulert records for this package has no fix yet. Plan around that one, or apply its workaround. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 2 vulnerabilities on record across 1 year, 2 in the last year.

What to do: Plan around the 1 vulnerability with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

Vulnerabilities on record 2 over 1 year · 2 in the last year i
Latest disclosure 27 Apr 2026 i
Highest CVSS n/a i
With no published fix 1 i

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

Scan your app free →

01 Versions

Which versions are affected

Vulert records these vulnerabilities by affected range rather than by individual release, so these are the ranges to check. Filter above to find the version you run.

Affected range	Vulnerabilities
up to 26.1 (exclusive)	1
all releases, no fix published yet	1

02 Disclosure history

How often vulnerabilities are recorded

2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 2 were recorded in the last 12 months.

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for pip

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CVE-2026-3219: pip Package Incorrect File Installation Due to Improper Archive Handling	N/A medium	No fix published	20 Apr 2026
CVE-2026-6357: pip Package Vulnerability Leading to Arbitrary Code Execution	N/A medium	26.1	27 Apr 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315