# CVE-2026-8328: FTP PASV SSRF, ftpcp() does not use actual peer address, trusts server-supplied PASV host address

> An attacker can exploit the Python ftplib module to perform Server-Side Request Forgery by manipulating PASV responses, bypassing previous security fixes.

- **Severity:** Medium 5.9 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:A/VC:N/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 13 May 2026
- **Updated:** 13 Aug 2026
- **Also known as:** ALPINE-CVE-2026-8328, AZL-86913, BELL-CVE-2026-8328, BIT-libpython-2026-8328, BIT-python-2026-8328, BIT-python-min-2026-8328, CLEANSTART-2026-AT54574, DEBIAN-CVE-2026-8328, ECHO-1e9d-9cbe-8622, GHSA-j989-fggp-qgp5, MINI-289f-xvvf-p4w2, MINI-6rhc-6fr5-fcjh, MINI-9v6q-v9gm-v6v8, MINI-cp9g-xvhp-qfxf, MINI-gf3q-c37g-36h2, PSF-0000-CVE-2026-8328, PSF-2026-24, ROOT-OS-DEBIAN-11-CVE-2026-8328, UBUNTU-CVE-2026-8328

## What is CVE-2026-8328?

CVE-2026-8328 is a medium-severity server-side request forgery vulnerability in CPython, published on 13 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-8328?

3 open source packages ship an affected version, including libpython, python and python-min.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `libpython` | Bitnami | All versions | 3.10.21, 3.11.16, 3.12.14, 3.13.14, 3.14.6 |
| `python` | Bitnami | All versions | 3.10.21, 3.11.16, 3.12.14, 3.13.14, 3.14.6 |
| `python-min` | Bitnami | All versions | 3.10.21, 3.11.16, 3.12.14, 3.13.14, 3.14.6 |

## How do I fix CVE-2026-8328?

Upgrade libpython to a fixed version for your release line: 3.10.21, 3.11.16, 3.12.14 or 3.13.14.

## Is CVE-2026-8328 being exploited?

There is no known exploitation of CVE-2026-8328 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-8328 and fix it if it is affected.

What it is: CVE-2026-8328 is a medium-severity server-side request forgery vulnerability in CPython, published on 13 May 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-8328 in the wild and no public exploit code.

Affected packages and fixed versions:
- libpython (Bitnami): affected all versions; fixed in 3.10.21, 3.11.16, 3.12.14, 3.13.14, 3.14.6
- python (Bitnami): affected all versions; fixed in 3.10.21, 3.11.16, 3.12.14, 3.13.14, 3.14.6
- python-min (Bitnami): affected all versions; fixed in 3.10.21, 3.11.16, 3.12.14, 3.13.14, 3.14.6

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-8328/ (Markdown: https://insights.sbomify.com/CVE-2026-8328/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-8328
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-8328
- OSV: https://osv.dev/vulnerability/CVE-2026-8328

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-8328/
Summaries are generated and may contain mistakes; the official description above is the record.