Skip to main content
Menu
CVEs

CVE

Fastify Multipart denial of service via temp file leak in file uploads

Affects @fastify/multipart from 3.0.0 before 10.1.4 in applications that call request.saveRequestFiles() to write uploads to disk. Fixed in 10.1.4.

CVE-2026-110710EUVD-2026-126371

Written by anthropic/claude-haiku-5.5 from the sources below. Verify against them.

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

7.5HighCNA
Exploited
No known exploitation
Fix
Fixed in 10.1.4
Who is exposed
Not reported

Do first: Upgrade to a fixed version: 10.1.4.

Published
Last modified
Reference
Last checked
44/100 · provisional
Unclear
74% of @fastify/multipart downloads last week were affected versions (3.4M).npm, 4.6M downloads in the last 7 days, read Nov 16, 2026
None on Exploit-DB, Metasploit or GitHub
  • Exploitation: none
  • Automatable: yes
  • Technical impact: partial

Summary

Remotely, without logging in, an unauthenticated client can disconnect after uploading a file to @fastify/multipart, leaving the temporary files saved by saveRequestFiles on disk. Repeating this can exhaust disk space and deny service to applications that save uploaded files.

Original description

@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.

Who should check

Teams running @fastify/multipart 3.0.0 through 10.1.3 in Fastify services that call request.saveRequestFiles(), especially handlers doing async work after the save

“Applications that call request.saveRequestFiles() are affected”

github.com

cve.now Index

44Pcve.now Index 44 of 100 · methodology v3 · provisional
  • Exploitation0/40No signal
  • Exposure20/25No login or user action needed, CISA rates it automatable · Unknown: Advisories don't say whether default setups are affected
  • Reach16/20@fastify/multipart: 4.6M downloads a week
  • Severity7.5/10CVSS 7.5
  • No patch0/5No signal

What would change the score

  • Would score about 89 if added to CISA KEV
  • Would score about 84 if CISA's SSVC rates exploitation active
  • Would score about 49 if advisories confirm default setups are exposed

Impact

  • Widely used

    @fastify/multipart has 4.6m weekly downloads.Source: npmjs.com

    260 packages depend on @fastify/multipart.Source: deps.dev

What to do

  • Upgrade to a fixed version: 10.1.4.

Check your systems with an agent

Paste this into a coding or ops agent. It checks your systems read-only and reports a table per asset.

Check whether my systems are affected by CVE-2026-110710 (@fastify/multipart vulnerable to Denial of Service via temporary file leak after client disconnect), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-110710 (entry last updated 2026-11-16):
Affected:
- npm package @fastify/multipart: from 3.0.0, fixed in 10.1.4
Fixed versions: 10.1.4.
Conditions (all must be true for the bug to be hit):
- Uses request.saveRequestFiles() to write uploads to disk (source: https://github.com/fastify/fastify-multipart/security/advisories/GHSA-r9rg-mfh6-f225)
- @fastify/multipart versions from 3.0.0 up to but not including 10.1.4 (source: https://github.com/fastify/fastify-multipart/security/advisories/GHSA-r9rg-mfh6-f225)
- Client disconnects after the upload is saved but before the handler writes the reply (source: https://github.com/fastify/fastify-multipart/security/advisories/GHSA-r9rg-mfh6-f225)
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
Attacker needs: network access, no login, no user action.
CISA KEV: CVE-2026-110710 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-110710 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Packages (npm): find every lockfile in each project and run the stack.check operation of the cve.now MCP server (execute) on each one. Compare the resolved versions, not the ranges a manifest declares, with the affected versions above. Include transitive dependencies.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://github.com/fastify/fastify-multipart/security/advisories/GHSA-r9rg-mfh6-f225
- https://cna.openjsf.org/security-advisories.html
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-110710
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-110710"}.

Timeline

  1. CVE published
  2. First seen by cve.now
  3. CISA SSVC assessment

    Exploitation: none · Automatable: yes · Technical impact: partial

  4. Record last updated

Affected versions

  • From 3.0.0 · fixed in 10.1.4

    Fixed in 10.1.4 (released Oct 15, 2026, 32 days before disclosure).

    The latest release, 10.1.9, is not affected.

Evidence 4

Vendor advisory · 1

Establishes: Affected and fixed versions.

  1. Advisory

CVE record · 2

Establishes: The identifier and description.

  1. Record
  2. Record

Other links · 1

  1. Link

Corrections

None so far.

Something wrong on this page? Report an error. Every fix is listed here.

Questions about CVE-2026-110710

Is CVE-2026-110710 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.Source: cve.now feed data

What does this mean?

When a client disconnects after an upload is saved but before the handler writes the reply, the temporary files are left on disk. A remote client can repeat this cheaply, filling the server's disk and causing a denial of service.Source: github.com

Which versions are affected by CVE-2026-110710?

@fastify/multipart (npm): from 3.0.0 before 10.1.4.Source: cve.now feed data

Am I affected, and how do I check?

Versions of @fastify/multipart from 3.0.0 up to but not including 10.1.4 are affected, but only applications that call request.saveRequestFiles(). To check the installed version, run npm ls @fastify/multipart in the project directory.Source: github.com

How do I fix CVE-2026-110710?

Upgrade @fastify/multipart to 10.1.4 or later, which is the listed fixed version.Source: github.com