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.5%, top 62% 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.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 5.9Exploit: None knownExposed: 0

A fix is available — apply it.

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

Published

May 13, 2026

Last Modified

August 13, 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.

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntupython3.14-venv (3.14.4-1ubuntu0.1) @ resolute2026-08-23ubuntu

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

(10 across 4 ecosystems)
Debian:11(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.10+dfsg-1 ... 7.3.9+dfsg-5 (53 versions)——
python2.72.7.18-10 ... 2.7.18-9 (10 versions)——
python3.93.9.10-1 ... 3.9.9-4 (29 versions)——
Debian:14(3)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.11-1 ... 3.13.9-1 (7 versions)3.13.14-1—
python3.143.14.0-1 ... 3.14.5~rc1-1 (23 versions)3.14.6-1—
Debian:12(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.11+dfsg-2 ... 7.3.23+dfsg-1 (29 versions)——
python3.113.11.2-6 ... 3.11.9-1 (28 versions)——
Debian:13(2)
PackageVulnerable rangeFixed inDependents
pypy37.3.19+dfsg-2 ... 7.3.23+dfsg-1 (11 versions)——
python3.133.13.5-2, 3.13.5-2+deb13u1, 3.13.5-2+deb13u23.13.5-2+deb13u3—

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 7× in last 7d / 72× 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 207 total refreshes for this CVE.

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

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 August 13, 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 0% probability of exploitation in the next 30 days, which ranks it in the top 61.9% of all scored CVEs.
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

See which npm, PyPI, Go, and Maven packages are affected by 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