CVE-2026-13346

MEDIUMNVD 6.56.5—
EchelonGraph scoreHIGH 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 — 5 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%CVSS: 6.5Exploit: None knownExposed: 0

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.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
21%
KEV
Not listed

Published

July 29, 2026

Last Modified

August 20, 2026

Advisory Details (2)

Auto-updated Jul 29, 2026
Upstream fix merged — awaiting tagged release. 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

Vendor Advisories for CVE-2026-13346(2)

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 / EcosystemFixed in / 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

(4 across 4 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 ... 26.1.2+dfsg-1 (7 versions)——

Weakness Classification(1)

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

Additional Vendor Advisories

(1)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

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

  1. 2026-08-25 15:01 UTCEG score recompute
  2. 2026-08-25 15:01 UTCVendor advisory
  3. 2026-08-25 15:01 UTCGHSA enrichment
  4. 2026-08-25 13:48 UTCEPSS rescore
  5. 2026-08-24 14:48 UTCEG score recompute
  6. 2026-08-24 14:48 UTCVendor advisory
  7. 2026-08-24 14:48 UTCGHSA enrichment
  8. 2026-08-23 14:35 UTCEG score recompute
  9. 2026-08-23 14:35 UTCVendor advisory
  10. 2026-08-23 14:35 UTCGHSA enrichment
  11. 2026-08-23 00:19 UTCEPSS rescore
  12. 2026-08-22 14:23 UTCEG score recompute
  13. 2026-08-22 14:23 UTCVendor advisory
  14. 2026-08-22 14:23 UTCGHSA enrichment
  15. 2026-08-21 23:48 UTCEPSS rescore
  16. 2026-08-21 14:10 UTCEG score recompute
  17. 2026-08-21 14:10 UTCVendor advisory
  18. 2026-08-21 14:10 UTCGHSA enrichment
  19. 2026-08-20 22:55 UTCEPSS rescore
  20. 2026-08-20 13:57 UTCEG score recompute▲ 0.90
  21. 2026-08-20 13:57 UTCVendor advisory
  22. 2026-08-20 13:57 UTCGHSA enrichment
  23. 2026-08-20 13:22 UTCNVD updateCVSS v3 → 6.5
  24. 2026-08-19 21:57 UTCEG score recompute
  25. 2026-08-19 21:57 UTCVendor advisory
Show 75 more
  1. 2026-08-19 21:57 UTCGHSA enrichment
  2. 2026-08-19 17:03 UTCEPSS rescore
  3. 2026-08-18 21:45 UTCEG score recompute
  4. 2026-08-18 21:45 UTCVendor advisory
  5. 2026-08-18 21:45 UTCGHSA enrichment
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 20:59 UTCEG score recompute
  8. 2026-08-17 20:59 UTCVendor advisory
  9. 2026-08-17 20:59 UTCGHSA enrichment
  10. 2026-08-16 20:47 UTCEG score recompute
  11. 2026-08-16 20:47 UTCVendor advisory
  12. 2026-08-16 20:47 UTCGHSA enrichment
  13. 2026-08-16 14:56 UTCEPSS rescore
  14. 2026-08-16 02:14 UTCEPSS rescore
  15. 2026-08-15 20:35 UTCEG score recompute
  16. 2026-08-15 20:35 UTCVendor advisory
  17. 2026-08-15 20:35 UTCGHSA enrichment
  18. 2026-08-15 01:30 UTCEPSS rescore
  19. 2026-08-14 20:22 UTCEG score recompute
  20. 2026-08-14 20:22 UTCVendor advisory
  21. 2026-08-14 20:22 UTCGHSA enrichment
  22. 2026-08-13 22:00 UTCEPSS rescore
  23. 2026-08-13 20:09 UTCVendor advisory
  24. 2026-08-13 20:09 UTCGHSA enrichment
  25. 2026-08-12 19:57 UTCEG score recompute
  26. 2026-08-12 19:57 UTCVendor advisory
  27. 2026-08-12 19:57 UTCGHSA enrichment
  28. 2026-08-12 13:50 UTCEPSS rescore
  29. 2026-08-11 19:44 UTCEG score recompute
  30. 2026-08-11 19:44 UTCVendor advisory
  31. 2026-08-11 19:44 UTCGHSA enrichment
  32. 2026-08-11 13:42 UTCEPSS rescore
  33. 2026-08-10 23:59 UTCEPSS rescore
  34. 2026-08-10 19:32 UTCVendor advisory
  35. 2026-08-10 19:32 UTCGHSA enrichment
  36. 2026-08-09 19:19 UTCEG score recompute
  37. 2026-08-09 19:19 UTCVendor advisory
  38. 2026-08-09 19:19 UTCGHSA enrichment
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-08 19:07 UTCEG score recompute
  41. 2026-08-08 19:07 UTCVendor advisory
  42. 2026-08-08 19:07 UTCGHSA enrichment
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-07 18:54 UTCEG score recompute
  45. 2026-08-07 18:54 UTCVendor advisory
  46. 2026-08-07 18:54 UTCGHSA enrichment
  47. 2026-08-06 18:42 UTCEG score recompute
  48. 2026-08-06 18:42 UTCVendor advisory
  49. 2026-08-06 18:42 UTCGHSA enrichment
  50. 2026-08-06 13:46 UTCEPSS rescore
  51. 2026-08-05 19:17 UTCEPSS rescore
  52. 2026-08-05 18:29 UTCVendor advisory
  53. 2026-08-05 18:29 UTCGHSA enrichment
  54. 2026-08-04 18:17 UTCEG score recompute
  55. 2026-08-04 18:17 UTCVendor advisory
  56. 2026-08-04 18:17 UTCGHSA enrichment
  57. 2026-08-04 15:09 UTCEPSS rescore
  58. 2026-08-04 10:38 UTCEPSS rescore
  59. 2026-08-03 18:05 UTCEG score recompute
  60. 2026-08-03 18:05 UTCVendor advisory
  61. 2026-08-03 18:05 UTCGHSA enrichment
  62. 2026-08-03 10:35 UTCEPSS rescore
  63. 2026-08-02 17:35 UTCEG score recompute
  64. 2026-08-02 17:35 UTCVendor advisory
  65. 2026-08-02 17:35 UTCGHSA enrichment
  66. 2026-08-02 02:26 UTCEPSS rescore
  67. 2026-08-01 17:23 UTCEG score recompute
  68. 2026-08-01 17:23 UTCVendor advisory
  69. 2026-08-01 17:23 UTCGHSA enrichment
  70. 2026-08-01 04:15 UTCEPSS rescore
  71. 2026-07-31 17:11 UTCVendor advisory
  72. 2026-07-31 17:11 UTCGHSA enrichment
  73. 2026-07-30 16:58 UTCEG score recompute
  74. 2026-07-30 16:58 UTCGHSA enrichment
  75. 2026-07-30 16:27 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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 78.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-13346, 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-13346

Explore →

Is Your Infrastructure Affected by CVE-2026-13346?

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

Start Free Scan →Browse All CVEs