CVE-2026-13346

MEDIUMNVD 6.56.5—
EchelonGraph scoreMEDIUM confidence

Score 6.5 from GitHub Security Advisory published 2026-07-29. NVD baseline CVSS 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 6.5Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

pip would incorrectly handle doubly-encoded package URLs from indexes allowing for files to be installed to arbitrary locations on disk even when installing wheels.

This vulnerability requires downloading or installing a package from a malicious package index to succeed, malicious packages alone are not able to exploit this vulnerability. Note that this vulnerability only materially impacts users running pip download with the --only-binary option as installing source distributions from an untrusted index is already an unsafe operation that executes code during install time.

CVSS v3
6.5
EG Score
6.5MEDIUMmedium confidence
EG Risk
29
EG Risk 29/100CISA SSVC

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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
CISA SSVC: Track at every mission impact level.
Action: A fix is available. Apply it within your standard update timelines.
EPSS PROB
0.3%
EPSS %ILE
20th
KEV
Not listed

CISA SSVCTrack 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). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

July 29, 2026

Last Modified

August 20, 2026

Advisory Details (2)

Auto-updated Jul 29, 2026
Patch available. Sources: github_pr.
generic

Mailman 3 [CVE-2026-13346] pip absolute path traversal during download from malicious package indexes - Security-announce - python.org

https://mail.python.org/archives/list/[email protected]/thread/L2BNQGGVQCEV7DROOORQ7WFKKFF2OOQX/
github_pr

Fix Link.filename decoding URL path twice

Fix merged in pypa/pip PR #14110 on 2026-07-01 — awaiting tagged release

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

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 ... 26.1.2+dfsg-1 (7 versions)
  • every version on: no fix on record
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
pip0.2 ... 9.0.3 (157 versions)
  • every version up to 26.2.0: fixed in 26.2.0
  • every version up to 26.2: fixed in 26.2
—

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 13× in last 7d / 58× 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 200 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-13346?
CVE-2026-13346 is a medium vulnerability published on July 29, 2026. pip would incorrectly handle doubly-encoded package URLs from indexes allowing for files to be installed to arbitrary locations on disk even when installing wheels. This vulnerability requires downloading or installing a package from a malicious package index to succeed, malicious packages alone…
When was CVE-2026-13346 disclosed?
CVE-2026-13346 was first published on July 29, 2026, with the most recent update on August 20, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-13346 actively exploited?
CVE-2026-13346 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (20th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-13346?
CVE-2026-13346 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-13346?
A fix for CVE-2026-13346 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-13346 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-13346

Explore →

Is Your Infrastructure Affected by CVE-2026-13346?

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