Skip to main content
VulnerabilityPublished

CVE-2026-117531: @fastify/multipart · Uncontrolled Resource Consumption

Affects @fastify/multipartSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.9 Medium : upgrade to 10.1.7 when convenient.

Data as of 2 Nov 2026, 11:12 UTC

CVSS 3.1 base score
5.9Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (openjs)CVSS 3.15.9
Patch
Available – fixed in 10.1.7
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 2 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2 Nov 2026.

What to do

Upgrade @fastify/multipart to 10.1.7.

Affected software

ProductAffectedFixed in
@fastify/multipart@fastify/multipartAffected
  • >=5.3.0 <10.1.7
Fixed in
  • 10.1.7
npm@fastify/multipartpkg:npm/@fastify/multipartOther threatsAffected
  • >=5.3.0 <10.1.7
Fixed in
  • 10.1.7

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Upgrade @fastify/multipart to version 10.1.7 or later. There is no workaround other than upgrading, as the fix involves proper error propagation in the plugin.

Description

@fastify/multipart versions 5.3.0 through 10.1.6 have a vulnerability where a parser error is not propagated to the file stream if a request body ends inside a file part without a closing boundary. This causes the file stream to be destroyed silently, leading to hanging requests and potential resource exhaustion. The issue is fixed in version 10.1.7.

References

Community reviews

Loading reviews…