CVE-2026-6357

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.1% (3rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week

Also known asEUVD-2026-25857 (ENISA EUVD) · PYSEC-2026-2876 (OSV.dev)Source: ENISA EUVD

5.3EG
EchelonGraph verdictMonitorRemediate within your standard update timelines (the SSVC decision on this page).
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.1%CVSS: 5.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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.3MEDIUMmedium confidence
EG Risk
24
EG Risk 24/100

EG Risk is EchelonGraph's 0–100 priority score. It fuses impact severity (EG Severity, the CVSS base score, never the KEV-floored or EPSS-lifted EG Score) with real-world exploitation and automatability, under weights EchelonGraph set by hand, so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner.

How it’s computed (value × EchelonGraph’s weight)
Severity53% × 45%
Impact severity (EG Severity): CVSS 5.3 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at every mission impact level.
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.1%
EPSS %ILE
3rd
KEV
Not listed

What the EG score is made of (scorer v4.0: the three questions the 0–10 score mixes, published apart · methodology)

The EG score (5.3): severity, escalated by confirmed exploitation. This CVE's 5.3 is its impact severity (EG Severity), not escalated.

EG Severity
5.3 MEDIUMCVSS-B, impact only: no KEV listing, EPSS or EG-KEV tier raises it.NVD CVSS v3 · CVSS v3.0 or v3.1
EG Likelihood
0.1% within 30 daysSource: FIRST EPSS. FIRST's exploitation probability, not an EchelonGraph model.
Confirmed exploitation
None on record (CISA KEV, EG-KEV Tier 1)Reported apart from the likelihood: an observed fact, not a probability.
EG Priority
SSVC Track at medium mission impactTrack at every mission impact level.CISA BOD 26-04: 60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.Each input and its source: the SSVC and BOD 26-04 blocks below.

SSVC (CISA's decision table, applied by EchelonGraph)Track at every mission impact level.

A fix is available. Apply it within your standard update timelines.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)60 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

April 27, 2026

Last Modified

April 27, 2026

Advisory Details (3)

Auto-updated Aug 3, 2026
Patch available. Sources: github_pr.
Web page

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
Web page

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 pull request

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(4)

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

Patch Availability(1)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-pip-main-26.2-0.1.hum12026-07-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(5 across 5 ecosystems)
Debian:11(1)
PackageVulnerable rangeFix by version rangeDependents
python-pip20.3.4-4 ... 26.1.2+dfsg-1 (37 versions)
  • every version on: no fix on record
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
python-pip23.0.1+dfsg-1 ... 26.1.2+dfsg-1 (22 versions)
  • every version on: no fix on record
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
python-pip25.1.1+dfsg-1 ... 26.1.2+dfsg-1 (7 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
python-pip25.1.1+dfsg-1, 25.2+dfsg-1, 25.3+dfsg-1, 26.0+dfsg-1, 26.0.1+dfsg-1
  • every version up to 26.1.1+dfsg-1: fixed in 26.1.1+dfsg-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pip0.2 ... 9.0.3 (154 versions)
  • every version up to 26.1: fixed in 26.1
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 9× in last 7d / 38× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 98 of 228 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 2 repeat rows among the latest 100 are merged into the row they repeat. The 130 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same vendor + same CWE)

Same vendor

1 shown

redhat:RHSA-2026:48788

Frequently asked(5)

What is CVE-2026-6357?
CVE-2026-6357 is a medium-severity vulnerability; its CVE record was 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 the CVE record for CVE-2026-6357 published?
The CVE record for CVE-2026-6357 was published on April 27, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of April 27, 2026; the record at its source may have been updated since.
Is CVE-2026-6357 actively exploited?
CVE-2026-6357 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.1% probability of exploitation in the next 30 days (3rd percentile of EPSS-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?
A fix for CVE-2026-6357 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-6357 are linked in the Vendor Advisories panel on this page.

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.

Book a Demo →Browse All CVEs