CVE
Fastify Multipart arbitrary file write in saveRequestFiles()
Only affects @fastify/multipart 7.4.0 up to 10.1.9 when registered with attachFieldsToBody set to true or 'keyValues'. Fixed in 10.1.9.
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:H/A:N
- Exploited
- No known exploitation
- Fix
- Fixed in 10.1.9
- Who is exposed
- Not reported
Do first: Upgrade to a fixed version: 10.1.9.
- Last modified
- Whether it needs action now or is a reference record, by fixed rules, with why. Last checked is when cve.now last re-read it.What do these mean? →
- Reference
- Last checked
- A 0-100 score for how much a CVE matters across the industry: exploitation, exposure, how widely the software is used, severity and whether a fix exists.What do these mean? →
- 41/100 · provisional
- How many real-world setups can hit the bug, from the vendor's advisory and CISA data. It does not know your setup.What do these mean? →
- Unclear
- The share of the registry's downloads of each affected package in the window that were versions inside the affected ranges. Downloads, not users or installs: CI runs and mirrors inflate the counts.
- 99.6% of @fastify/multipart downloads last week were affected versions (4.6M).npm, 4.6M downloads in the last 7 days, read Nov 16, 2026
- Whether working attack code is public (Exploit-DB, Metasploit, Nuclei or GitHub). Public code makes attacks easier.What do these mean? →
- None on Exploit-DB, Metasploit or GitHub
Summary
The @fastify/multipart plugin, when registered with the attachFieldsToBody option, lets an unauthenticated attacker over the network send a crafted JSON request or JSON-typed multipart field that makes the saveRequestFiles helper write attacker-chosen bytes to the temporary directory while skipping upload hooks and file limits. Applications that use the returned filename, which is not reduced to its basename, as a write destination can also be tricked into writing files to arbitrary relative paths.
Original description
@fastify/multipart is the official Fastify plugin for handling multipart/form-data uploads. In versions 7.4.0 through 10.1.8, when the plugin is registered with the attachFieldsToBody option, the saveRequestFiles helper treats any object in the parsed request body that carries truthy file and buffer properties as an uploaded file. An unauthenticated client can forge such an object through a plain JSON request or a JSON-typed multipart field, so attacker-chosen bytes are written to the temporary directory while upload hooks and the file count and size limits are skipped, and the saved entry keeps the attacker's filename verbatim instead of being reduced to its basename. Because that filename can contain parent directory segments, applications that use it as a write destination, as the project README example does, are exposed to an arbitrary relative-path file write from a single request. The issue is fixed in @fastify/multipart 10.1.9, and users should upgrade to 10.1.9 or later. As a workaround, call saveRequestFiles only after confirming the request is multipart, and reduce each returned filename to its basename or validate it against an allowlist before using it as a destination.
Who should check
Teams running @fastify/multipart 7.4.0 through 10.1.8 with attachFieldsToBody set to true or 'keyValues', including apps that call saveRequestFiles and use its filenames as write destinations.
“when registered with attachFieldsToBody: true or 'keyValues'”
cve.now Index
- Exploitation?/40Unknown. No CISA SSVC exploitation rating yet
- Exposure17/25No login or user action needed, reachable over the network without a login · 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 86 if added to CISA KEV
- Would score about 81 if CISA's SSVC rates exploitation active
- Would score about 46 if advisories confirm default setups are exposed
Impact
What to do
Upgrade to a fixed version: 10.1.9.
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-124289 (@fastify/multipart vulnerable to arbitrary file write via type confusion in saveRequestFiles()), 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-124289 (entry last updated 2026-11-16):
Affected:
- npm package @fastify/multipart: from 7.4.0, fixed in 10.1.9
Fixed versions: 10.1.9.
Conditions (all must be true for the bug to be hit):
- Plugin registered with attachFieldsToBody set to true or 'keyValues'. (source: https://github.com/fastify/fastify-multipart/security/advisories/GHSA-gmhr-r4mc-w935)
- Affected @fastify/multipart versions from 7.4.0 up to but not including 10.1.9. (source: https://github.com/fastify/fastify-multipart/security/advisories/GHSA-gmhr-r4mc-w935)
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-124289 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-124289 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-gmhr-r4mc-w935
- 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-124289
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-124289"}.Timeline
- CVE published
- First seen by cve.now
Affected versions
From 7.4.0 · fixed in 10.1.9
Fixed in 10.1.9 (released Nov 16, 2026, the day of disclosure).
The latest release, 10.1.9, is not affected.
Evidence 4
Vendor advisory · 1
Establishes: Affected and fixed versions.
- Advisory
CVE record · 2
Establishes: The identifier and description.
- Record
- Record
Other links · 1
- Link
Corrections
None so far.
Something wrong on this page? Report an error. Every fix is listed here.
Questions about CVE-2026-124289
Is CVE-2026-124289 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?
A forged file in a request body can make attacker-chosen bytes get written to the temporary directory under a filename that contains path traversal. An application that uses the returned filename as a destination is then turned into an arbitrary relative-path file write by a single request.Source: github.com
Which versions are affected by CVE-2026-124289?
@fastify/multipart (npm): from 7.4.0 before 10.1.9.Source: cve.now feed data
Am I affected, and how do I check?
Versions from 7.4.0 up to but not including 10.1.9 are affected, and only when the plugin is registered with attachFieldsToBody set to true or 'keyValues'. To check, look at the installed version with `npm ls @fastify/multipart` and at the attachFieldsToBody option in the plugin registration.Source: github.com
How do I fix CVE-2026-124289?
Upgrade @fastify/multipart to 10.1.9 or later, which is the fixed version in the affected range.Source: github.com