CVE-2026-6357

CVE-2026-6357 is a medium-severity vulnerability with a CVSS 4.0 base score of 5.3. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-829.

Key facts

Description

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.

Frequently asked questions

What is CVE-2026-6357?
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.
How severe is CVE-2026-6357?
CVE-2026-6357 has a CVSS 4.0 base score of 5.3, rated medium severity.
Is CVE-2026-6357 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (4th percentile), an estimate of the probability of exploitation in the next 30 days.
How do I fix CVE-2026-6357?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-6357 have an EU (EUVD) identifier?
Yes. CVE-2026-6357 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-25857.
When was CVE-2026-6357 published?
CVE-2026-6357 was published on 2026-04-27 and last updated on 2026-06-17.

References

Other CWE-829 vulnerabilities

Browse all CWE-829 vulnerabilities →