CVE-2026-8328

MEDIUMPre-NVD 5.95.9—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.9 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 68% 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, secondary
5.9
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.9Exploit: NoneExposed: 0

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

The ftpcp() function in Lib/ftplib.py was not updated when CVE-2021-4189 was fixed. While makepasv() was patched to replace server-supplied PASV host addresses with the actual peer address (getpeername()[0]), ftpcp() still calls parse227() directly and passes the raw attacker-controllable IP address and port to target.sendport(). This patch is related to CVE-2021-4189.

CVSS v3
5.9
EG Score
5.9(medium)
EPSS
37.8%
KEV
Not listed

Published

May 13, 2026

Last Modified

June 30, 2026

Advisory Details (8)

Auto-updated Jun 14, 2026
Upstream fix merged — awaiting tagged release. Sources: github_commit, github_pr.
generic

Mailman 3 [CVE-2026-8328] FTP PASV SSRF, ftpcp() does not use actual peer address, trusts server-supplied PASV host address - Security-announce - python.org

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

gh-87451: Apply CVE-2021-4189 PASV fix to ftplib.ftpcp()

Fix merged in python/cpython PR #149648 on 2026-05-13 — awaiting tagged release

https://github.com/python/cpython/pull/149648
generic

ftplib should not use the host from the PASV response · Issue #87451 · python/cpython · GitHub

https://github.com/python/cpython/issues/87451
github_commit

commit eac4fe3b2c77 (python/cpython)

Fix landed in python/cpython commit eac4fe3b2c77 — awaiting tagged release

https://github.com/python/cpython/commit/eac4fe3b2c77693790a5ef7dfab127c1fee81bf9
github_commit

commit c88704431ea3 (python/cpython)

Fix landed in python/cpython commit c88704431ea3 — awaiting tagged release

https://github.com/python/cpython/commit/c88704431ea3248ca769384c13856330976fac1d
github_commit

commit bb3446dda6c4 (python/cpython)

Fix landed in python/cpython commit bb3446dda6c4 — awaiting tagged release

https://github.com/python/cpython/commit/bb3446dda6c49b32e67c11dbbbf221b40be00763
github_commit

commit 7d95a1dc7382 (python/cpython)

Fix landed in python/cpython commit 7d95a1dc7382 — awaiting tagged release

https://github.com/python/cpython/commit/7d95a1dc7382b55cba7fdd6a110336077584a4f0
github_commit

commit 5dadc64673ce (python/cpython)

Fix landed in python/cpython commit 5dadc64673ce — awaiting tagged release

https://github.com/python/cpython/commit/5dadc64673ce875ebfb24163907777dae0f6ca06

Vendor Advisories for CVE-2026-8328(2)

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

Weakness Classification(1)

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

Data Freshness Timeline

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

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-8328?
CVE-2026-8328 is a medium vulnerability published on May 13, 2026. The ftpcp() function in Lib/ftplib.py was not updated when CVE-2021-4189 was fixed. While makepasv() was patched to replace server-supplied PASV host addresses with the actual peer address (getpeername()[0]), ftpcp() still calls parse227() directly and passes the raw attacker-controllable IP…
When was CVE-2026-8328 disclosed?
CVE-2026-8328 was first published in the National Vulnerability Database on May 13, 2026, with the most recent update on June 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-8328 actively exploited?
CVE-2026-8328 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 37.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-8328?
CVE-2026-8328 has a CVSS v3 base score of 5.9 (NVD).
How do I remediate CVE-2026-8328?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-8328, 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

Explore the affected products and dependency analysis for CVE-2026-8328

Explore →

Is Your Infrastructure Affected by CVE-2026-8328?

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

Start Free Scan →Browse All CVEs