# CVE-2026-41324: basic-ftp vulnerable to denial of service via unbounded memory consumption in Client.list()

> A malicious FTP server can cause a Node.js application using basic-ftp to crash via memory exhaustion during directory listing.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** CLEANSTART-2026-LZ49764, CLEANSTART-2026-PE96268, DEBIAN-CVE-2026-41324, ECHO-a4e9-52ab-d2eb, GHSA-rp42-5vxx-qpwr, MINI-34mp-qfqx-w95w, MINI-36f3-hr43-vrxq, MINI-3q78-pc4r-7cq7, MINI-5q4j-g6mh-27m8, MINI-64h2-gjgp-wvg3, MINI-6q6j-m2g4-5h79, MINI-92v6-jrhr-rgjw, MINI-976j-8rvc-7fh7, MINI-frg4-86c8-hfmp, MINI-fvh6-cj9p-w384, MINI-h7mq-qj52-vpcq, MINI-jj2q-2fpx-37j5, MINI-jqj8-qc82-pqg8, MINI-m4vp-ggwj-6m4m, MINI-m5ww-3j5h-f8wv, MINI-p85v-c7h3-mff5, MINI-qc93-3m82-rfhv, MINI-qwxh-477f-x8jr, MINI-vf88-8vpf-9qx8, MINI-vvfh-f64w-22j3, MINI-wr8g-85r2-7pvr, ROOT-APP-NPM-CVE-2026-41324, ROOT-APP-NPM-GHSA-rp42-5vxx-qpwr, UBUNTU-CVE-2026-41324

## What is CVE-2026-41324?

CVE-2026-41324 is a high-severity denial of service vulnerability in patrickjuchli basic-ftp, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

basic-ftp is an FTP client for Node.js. Versions prior to 5.3.0 are vulnerable to denial of service through unbounded memory growth while processing directory listings from a remote FTP server. A malicious or compromised server can send an extremely large or never-ending listing response to `Client.list()`, causing the client process to consume memory until it becomes unstable or crashes. Version 5.3.0 fixes the issue.

Weakness: CWE-770 (Allocation of Resources Without Limits or Throttling), CWE-400 (Uncontrolled Resource Consumption)

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

2 open source packages ship an affected version, including basic-ftp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `basic-ftp` | npm | All versions | 5.3.0 |
| `basic-ftp` | npm | All versions | 5.3.0 |

Products: Patrickjuchli Basic-Ftp.

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

Upgrade basic-ftp to 5.3.0 or later.

## Is CVE-2026-41324 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41324 exists.

## Other vulnerabilities in patrickjuchli basic-ftp

- [CVE-2026-27699](https://insights.sbomify.com/CVE-2026-27699/): Basic FTP has Path Traversal Vulnerability in its downloadToDir() method (critical 9.1)
- [CVE-2026-39983](https://insights.sbomify.com/CVE-2026-39983/): FTP Command Injection via CRLF in basic-ftp (high 8.6)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-41324 is a high-severity denial of service vulnerability in patrickjuchli basic-ftp, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41324 exists.

Affected packages and fixed versions:
- basic-ftp (npm): affected all versions; fixed in 5.3.0
- basic-ftp (npm): affected all versions; fixed in 5.3.0

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-41324/ (Markdown: https://insights.sbomify.com/CVE-2026-41324/index.md)
```

## Sources

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

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