CVE-2026-1703

LOWNVD 2.02.0
EchelonGraph scoreMEDIUM confidence

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

This low-severity CVE scores 2.0 under NVD CVSS v3. EPSS exploit probability: 0.4% (37th 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 — 5 sources updated this week

Also known asEUVD-2026-5106 (ENISA EUVD) · GHSA-6vgw-5pg2-w6jp (GitHub Security Advisories) · PYSEC-2026-1796 (OSV.dev)Source: ENISA EUVD

2.0EG
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.4%CVSS: 2.0Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

When pip is installing and extracting a maliciously crafted wheel archive, files may be extracted outside the installation directory. The path traversal is limited to prefixes of the installation directory, thus isn't able to inject or overwrite executable files in typical situations.

CVSS v3
2.0
EG Score
2.0LOWmedium confidence
EG Risk
9
EG Risk 9/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)
Severity20% × 45%
Impact severity (EG Severity): CVSS 2.0 of 10. Never the KEV-floored or EPSS-lifted EG Score.
Exploitation0.4% × 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.4%
EPSS %ILE
37th
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 (2.0): severity, escalated by confirmed exploitation. This CVE's 2.0 is its impact severity (EG Severity), not escalated.

EG Severity
2.0 LOWCVSS-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.4% within 30 daysSource: FIRST EPSS (model v2026.06.15, score date 2026-10-31). 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, and whom BOD 26-04 binds: 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.

The score's inputs: 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

February 2, 2026

Last Modified

June 17, 2026

References (3)

Vendor Advisories for CVE-2026-1703(5)

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

Patch Availability(2)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
redhatpython-pip-main-26.0.1-2.1.hum12026-04-10redhat
pippip @ 26.0 (fixes < 26.0)—ghsa

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
  • every version up to 26.0+dfsg-1: fixed in 26.0+dfsg-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pip0.2 ... 9.0.3 (152 versions)
  • every version up to 26.0: fixed in 26.0
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 12× in last 7d / 42× 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 100 of 221 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. None are among the latest 100 rows. The 121 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

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

Related CVEs(same product + same CWE)

Frequently asked(5)

What is CVE-2026-1703?
CVE-2026-1703 is a low-severity vulnerability; its CVE record was published on February 2, 2026. When pip is installing and extracting a maliciously crafted wheel archive, files may be extracted outside the installation directory. The path traversal is limited to prefixes of the installation directory, thus isn't able to inject or overwrite executable files in typical situations.
When was the CVE record for CVE-2026-1703 published?
The CVE record for CVE-2026-1703 was published on February 2, 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 June 17, 2026; the record at its source may have been updated since.
Is CVE-2026-1703 actively exploited?
CVE-2026-1703 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.4% probability of exploitation in the next 30 days (37th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-1703?
CVE-2026-1703 has a CVSS v3 base score of 2.0 (NVD).
How do I remediate CVE-2026-1703?
A fix for CVE-2026-1703 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-1703 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-1703

Explore →

Is Your Infrastructure Affected by CVE-2026-1703?

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

Book a Demo →Browse All CVEs