---
id: "CVE-2026-110710"
page: "https://infrastack.ai/live/CVE-2026-110710"
kind: "vulnerability"
aliases: ["CVE-2026-110710"]
title: "@fastify/multipart: disconnected uploads leave temp files on disk"
severity: "high"
cvss: 7.5
epss: null
exploited: false
status: "open"
category: "package"
products: []
ecosystems: []
tags: ["fastify", "file-uploads", "node", "package", "self-hosted"]
not_affected_if: ["no-saverequestfiles", "trusted-clients-only", "version-10.1.4-or-later"]
published_at: "2026-11-16T13:17:18+00:00"
first_seen_at: "2026-11-16T13:37:55+00:00"
updated_at: "2026-11-16T13:38:44+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-110710", "first_seen_at": "2026-11-16T13:37:55+00:00"}]
exploit_sources: []
---

# @fastify/multipart: disconnected uploads leave temp files on disk

Link for people: https://infrastack.ai/live/CVE-2026-110710 (this .md is for agents)

When a client finishes an upload and disconnects before the handler replies, saveRequestFiles temp files are never cleaned up. An unauthenticated client can repeat this to fill the disk and deny service.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the installed version with `npm ls @fastify/multipart` and compare it against the fixed release.
- Look for use of `saveRequestFiles` in the application code.

## Fix

- `@fastify/multipart` `10.1.4` or later.

## Timeline

- 2026-11-16T13:37:55+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-110710

## Documents

- [advisory] Vendor advisory: github.com https://github.com/fastify/fastify-multipart/security/advisories/GHSA-r9rg-mfh6-f225

## From the sources

@fastify/multipart is the official Fastify plugin for handling multipart/form-data uploads. In versions 3.0.0 through 10.1.3, temporary files written by the saveRequestFiles helper are removed only by a response hook that runs when the response finishes or errors. When a client completes an upload and then disconnects before the handler writes the reply, for example while the handler scans, hashes or forwards the file, the response only emits a close event, the cleanup hook never runs, and the saved files are left on disk. An unauthenticated client can repeat this cheaply to exhaust disk space and deny service to applications that save uploaded files to disk. The issue is fixed in @fastify/multipart 10.1.4, and users should upgrade to 10.1.4 or later. As a workaround, avoid saving request files for untrusted clients, or clean the saved files from a close handler on the raw response so removal also happens when the client disconnects.

---

_Free to read, with fair use of about 60 pages a minute. For higher limits or API access: sales@infrastack.ai_
