Skip to content

← Public intelligence

npm package

@fastify/multipart

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

2 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 7.5npmAmendedPublished

    Unlimited consumption of resources in @fastify/multipart

    CVE-2025-24033 · GHSA-27c6-mcxv-x3fh

    Affected
    • npm @fastify/multipart <= 8.3.0; >= 9.0.0, < 9.0.3
    Fixed in
    9.0.38.3.1· Vendor fix available
    Issue
    Impact The saveRequestFiles function does not delete the uploaded temporary files when user cancels the request. Patches Fixed in version 8.3.1 and 9.0.3 Workarounds Do not use saveRequestFiles. References This was identified in https://github.com/fastify/fastify-multipart/issues/546 and fixed in https://github.com/fastify/fastify-multipart/pull/567.

    Recommended action: Upgrade to 9.0.3 or 8.3.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →
  2. High, CVSS 7.5npmAmendedPublished

    Denial of service due to unlimited number of parts

    CVE-2023-25576 · GHSA-hpp2-2cr5-pf6g

    Affected
    • npm @fastify/multipart < 6.0.1; >= 7.0.0, < 7.4.1
    Fixed in
    6.0.17.4.1· Vendor fix available
    Issue
    Impact The multipart body parser accepts an unlimited number of file parts. The multipart body parser accepts an unlimited number of field parts. The multipart body parser accepts an unlimited number of empty parts as field parts. Patches This is fixed in v7.4.1 (for Fastify v4.x) and v6.0.1 (for Fastify v3.x). Workarounds There are no known workaround. References Reported at https://hackerone.com/reports/1816195.

    Recommended action: Upgrade to 7.4.1 or 6.0.1 by release line, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:osv.dev (1)github.com (2)Source checked Evidence →