Fastify Multipart Fixes Temporary-File Leaks and Forged Upload Writes

P1 — VALIDATE AND UPDATEHigh · 7.5 (CVSS v3.1 for each advisory)EXPLOITATION: NOT STATED

Quick Answer

Upgrade @fastify/multipart to 10.1.9 or later. Check saveRequestFiles() routes for cleanup after disconnects and safe handling of returned filenames.

Confirm Scope And Apply The Supported Remediation

What to do now: Identify multipart package versions, saveRequestFiles() callers, attachFieldsToBody settings, temporary directories and code that copies uploaded files to final destinations. Review asynchronous processing after saving uploads and any route that accepts non-multipart bodies. Determine whether returned filename values influence a destination path without basename or allowlist checks. Deploy 10.1.9 or later. For an interim control, require request.isMultipart(), validate destination filenames and invoke cleanRequestFiles() on response close where appropriate for the handler lifecycle. Verify that completed, rejected and disconnected uploads leave no unexpected temporary files. Test JSON and multipart field rejection, upload hooks and path containment; retain package, disk-usage and regression evidence.

Open the authoritative advisory

Last verified: 2026-11-16 UTC. Recheck the authoritative advisory and supported distribution channel before changing production.

Scope And Authority

Product scope@fastify/multipart request.saveRequestFiles()
AdvisoryGHSA-r9rg-mfh6-f225 / GHSA-gmhr-r4mc-w935
CVEsCVE-2026-110710, CVE-2026-124289
Authoritative release date2026-11-16T10:52:20Z — earliest project advisory in this group; individual publication times are listed below.
Authority revision dateNo separate material advisory revision is confirmed.
Affected versionsTemporary-file leakage affects 3.0.0 through 10.1.3. Forged-file handling affects 7.4.0 through 10.1.8 when attachFieldsToBody is enabled and saveRequestFiles() processes attacker-controlled objects.
Fixed version@fastify/multipart 10.1.9 or later addresses both issues; temporary-file cleanup was fixed in 10.1.4
CVSS base score7.5 (CVSS v3.1 for each advisory)
CVSS severityHigh
Exploitation statusThe cited Fastify project advisories do not confirm exploitation in the wild.; no exploitation claim is inferred.

What Changed

Two advisories describe files left behind after a client disconnects and type confusion that lets request objects masquerade as uploaded files. The latter can bypass upload hooks and limits; relative-path writes depend on how the application uses the returned filename.

Advisory-Specific Version Boundaries

<a href="https://github.com/fastify/fastify-multipart/security/advisories/GHSA-r9rg-mfh6-f225">CVE-2026-110710</a>Affected: >= 3.0.0, < 10.1.4. Fixed: 10.1.4. CVSS v3.1: 7.5; High. Published: 2026-11-16T10:52:20Z.
<a href="https://github.com/fastify/fastify-multipart/security/advisories/GHSA-gmhr-r4mc-w935">CVE-2026-124289</a>Affected: >= 7.4.0, < 10.1.9. Fixed: 10.1.9. CVSS v3.1: 7.5; High. Published: 2026-11-16T11:10:34Z.

What To Validate Now

  1. Inventory. Identify multipart package versions, saveRequestFiles() callers, attachFieldsToBody settings, temporary directories and code that copies uploaded files to final destinations.
  2. Establish applicability. Review asynchronous processing after saving uploads and any route that accepts non-multipart bodies. Determine whether returned filename values influence a destination path without basename or allowlist checks.
  3. Remediate. Deploy 10.1.9 or later. For an interim control, require request.isMultipart(), validate destination filenames and invoke cleanRequestFiles() on response close where appropriate for the handler lifecycle.
  4. Validate. Verify that completed, rejected and disconnected uploads leave no unexpected temporary files. Test JSON and multipart field rejection, upload hooks and path containment; retain package, disk-usage and regression evidence.
  5. Retain evidence. Preserve asset and owner identifiers, the applicability decision, before-and-after versions, change approval, installation output, validation results, and any exception or rollback record.

Operational Cautions

Version 10.1.4 fixes cleanup only; it does not address the later forged-file issue. Review retained temporary files through the service retention policy and avoid deleting files belonging to active jobs.

Evidence To Retain

  • Exact product, release stream, package or application version, enabled feature, environment, and accountable owner.
  • UTC timestamps, authority revision, approved change record, installer or package-manager output, and resulting version.
  • Relevant logs and monitoring evidence, test results, exceptions, compensating controls, and rollback decisions.

Related TechGeeks Resources

Authoritative References

Correction policy: If the authority changes affected versions, fixed versions, severity, exploitation information, mitigations, or required action, TechGeeks will update this notice and its verification date.