CVE-2026-6357

MEDIUMNVD 5.35.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.1%, top 96% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.3Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity53% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
4%
KEV
Not listed

Published

April 27, 2026

Last Modified

April 27, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
Upstream fix merged — awaiting tagged release. Sources: github_pr.
generic

oss-security - [CVE-2026-6357] pip self-update functionality can import newly installed modules after wheel installation

http://www.openwall.com/lists/oss-security/2026/04/27/7
generic

What's new in pip 26.1 - lockfiles and dependency cooldowns! – Richard Si

https://ichard26.github.io/blog/2026/04/whats-new-in-pip-26.1/#security-fixes
github_pr

Split the pip self-version check to get info before run

Fix merged in pypa/pip PR #13923 on 2026-04-25 — awaiting tagged release

https://github.com/pypa/pip/pull/13923

Vendor Advisories for CVE-2026-6357(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFixed inDependents
python-pip20.3.4-4 ... 26.1.2+dfsg-1 (37 versions)——
Debian:12(1)
PackageVulnerable rangeFixed inDependents
python-pip23.0.1+dfsg-1 ... 26.1.2+dfsg-1 (22 versions)——
Debian:13(1)
PackageVulnerable rangeFixed inDependents
python-pip25.1.1+dfsg-1 ... 26.1.2+dfsg-1 (7 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
python-pip25.1.1+dfsg-1, 25.2+dfsg-1, 25.3+dfsg-1, 26.0+dfsg-1, 26.0.1+dfsg-126.1.1+dfsg-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
pip0.2 ... 9.0.3 (154 versions)26.1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 181 total refreshes for this CVE.

  1. 2026-09-15 03:12 UTCEPSS rescore
  2. 2026-09-12 15:02 UTCEPSS rescore
  3. 2026-09-11 14:53 UTCEPSS rescore
  4. 2026-09-11 09:37 UTCEPSS rescore
  5. 2026-09-08 22:01 UTCEPSS rescore
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-05 15:31 UTCEPSS rescore
  9. 2026-09-04 05:07 UTCEPSS rescore
  10. 2026-09-04 01:46 UTCOSV refresh
  11. 2026-09-02 14:12 UTCEPSS rescore
  12. 2026-09-01 13:54 UTCEPSS rescore
  13. 2026-09-01 04:40 UTCEPSS rescore
  14. 2026-08-30 19:17 UTCEPSS rescore
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:42 UTCEPSS rescore
  17. 2026-08-26 14:47 UTCEPSS rescore
  18. 2026-08-25 13:49 UTCEPSS rescore
  19. 2026-08-23 00:19 UTCEPSS rescore
  20. 2026-08-21 23:49 UTCEPSS rescore
  21. 2026-08-20 22:56 UTCEPSS rescore
  22. 2026-08-19 17:04 UTCEPSS rescore
  23. 2026-08-18 13:49 UTCEPSS rescore
  24. 2026-08-18 13:49 UTCEPSS rescore
  25. 2026-08-17 14:03 UTCEG score recompute
Show 75 more
  1. 2026-08-17 14:03 UTCVendor advisory
  2. 2026-08-17 13:47 UTCEPSS rescore
  3. 2026-08-16 14:56 UTCEPSS rescore
  4. 2026-08-16 14:56 UTCEPSS rescore
  5. 2026-08-16 05:38 UTCEG score recompute
  6. 2026-08-16 05:38 UTCVendor advisory
  7. 2026-08-16 02:15 UTCEPSS rescore
  8. 2026-08-15 01:31 UTCEPSS rescore
  9. 2026-08-14 04:01 UTCEG score recompute
  10. 2026-08-14 04:01 UTCVendor advisory
  11. 2026-08-13 22:00 UTCEPSS rescore
  12. 2026-08-12 17:42 UTCEG score recompute
  13. 2026-08-12 17:42 UTCVendor advisory
  14. 2026-08-12 13:51 UTCEPSS rescore
  15. 2026-08-11 16:39 UTCEG score recompute
  16. 2026-08-11 16:39 UTCVendor advisory
  17. 2026-08-11 00:00 UTCEPSS rescore
  18. 2026-08-10 12:46 UTCEG score recompute
  19. 2026-08-10 12:46 UTCVendor advisory
  20. 2026-08-09 13:47 UTCEPSS rescore
  21. 2026-08-09 12:37 UTCEG score recompute
  22. 2026-08-09 12:37 UTCVendor advisory
  23. 2026-08-08 16:37 UTCEPSS rescore
  24. 2026-08-08 12:21 UTCEG score recompute
  25. 2026-08-08 12:21 UTCVendor advisory
  26. 2026-08-07 12:24 UTCEG score recompute
  27. 2026-08-07 12:24 UTCVendor advisory
  28. 2026-08-06 13:47 UTCEPSS rescore
  29. 2026-08-05 22:49 UTCEG score recompute
  30. 2026-08-05 22:49 UTCVendor advisory
  31. 2026-08-05 19:17 UTCEPSS rescore
  32. 2026-08-05 19:17 UTCEPSS rescore
  33. 2026-08-04 15:10 UTCEPSS rescore
  34. 2026-08-04 10:39 UTCEPSS rescore
  35. 2026-08-03 20:53 UTCEG score recompute
  36. 2026-08-03 20:53 UTCVendor advisory
  37. 2026-08-03 10:36 UTCEPSS rescore
  38. 2026-08-02 10:26 UTCEG score recompute
  39. 2026-08-02 10:26 UTCVendor advisory
  40. 2026-08-02 02:27 UTCEPSS rescore
  41. 2026-08-01 04:16 UTCEPSS rescore
  42. 2026-07-30 16:28 UTCEPSS rescore
  43. 2026-07-30 01:30 UTCEPSS rescore
  44. 2026-07-28 15:37 UTCEPSS rescore
  45. 2026-07-27 14:14 UTCEPSS rescore
  46. 2026-07-26 14:54 UTCEPSS rescore
  47. 2026-07-26 14:54 UTCEPSS rescore
  48. 2026-07-25 14:18 UTCEPSS rescore
  49. 2026-07-25 14:18 UTCEPSS rescore
  50. 2026-07-24 14:18 UTCEPSS rescore
  51. 2026-07-24 14:18 UTCEPSS rescore
  52. 2026-07-23 14:18 UTCEPSS rescore
  53. 2026-07-23 14:18 UTCEPSS rescore
  54. 2026-07-23 03:22 UTCEG score recompute
  55. 2026-07-22 14:08 UTCEPSS rescore
  56. 2026-07-22 14:08 UTCEPSS rescore
  57. 2026-07-21 15:25 UTCEPSS rescore
  58. 2026-07-21 15:25 UTCEPSS rescore
  59. 2026-07-20 17:08 UTCEPSS rescore
  60. 2026-07-19 22:08 UTCOSV refresh
  61. 2026-07-19 14:31 UTCEPSS rescore
  62. 2026-07-19 02:29 UTCEPSS rescore
  63. 2026-07-18 10:04 UTCEPSS rescore
  64. 2026-07-16 17:03 UTCEPSS rescore
  65. 2026-07-15 16:57 UTCEPSS rescore
  66. 2026-07-15 02:00 UTCEPSS rescore
  67. 2026-07-15 02:00 UTCEPSS rescore
  68. 2026-07-13 22:31 UTCEPSS rescore
  69. 2026-07-13 06:13 UTCEPSS rescore
  70. 2026-07-13 06:13 UTCEPSS rescore
  71. 2026-07-12 05:46 UTCEPSS rescore
  72. 2026-07-11 08:27 UTCEPSS rescore
  73. 2026-07-11 08:27 UTCEPSS rescore
  74. 2026-07-09 19:10 UTCEPSS rescore
  75. 2026-07-09 19:10 UTCEPSS rescore

Frequently asked(5)

What is CVE-2026-6357?
CVE-2026-6357 is a medium vulnerability published on April 27, 2026. 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…
When was CVE-2026-6357 disclosed?
CVE-2026-6357 was first published in the National Vulnerability Database on April 27, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-6357 actively exploited?
CVE-2026-6357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 96.4% of all scored CVEs.
What is the CVSS score of CVE-2026-6357?
CVE-2026-6357 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-6357?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-6357, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-6357

Explore →

Is Your Infrastructure Affected by CVE-2026-6357?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs