How severe is GHSA-hpp2-2cr5-pf6g?

GHSA-hpp2-2cr5-pf6g has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-hpp2-2cr5-pf6g?

GHSA-hpp2-2cr5-pf6g affects the following packages: @fastify/multipart (npm), @fastify/multipart (npm). Ecosystems affected: npm.

How do I fix GHSA-hpp2-2cr5-pf6g?

Update @fastify/multipart to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hpp2-2cr5-pf6g is resolved across your whole dependency graph.

How do I detect GHSA-hpp2-2cr5-pf6g in my npm dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @fastify/multipart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-hpp2-2cr5-pf6g if there is no patch (or I can't update yet)?

Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Is GHSA-hpp2-2cr5-pf6g actively exploited in the wild?

No public exploit code has been indexed for GHSA-hpp2-2cr5-pf6g yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for GHSA-hpp2-2cr5-pf6g?

GHSA-hpp2-2cr5-pf6g has an EPSS (Exploit Prediction Scoring System) score of 1.5%, placing it in the 74th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-hpp2-2cr5-pf6g?

GHSA-hpp2-2cr5-pf6g is classified as CWE-770 (CWE-770). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-hpp2-2cr5-pf6g published, and has it been updated?

GHSA-hpp2-2cr5-pf6g was published on February 14, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

📦

📦 npm

Not in CISA KEV

HIGH severity

Denial of service due to unlimited number of partsGHSA-hpp2-2cr5-pf6g

HIGHFix: fastify/fastify-multipart@85be81b

GHSA-hpp2-2cr5-pf6g is a high-severity (CVSS 7.5) CWE-770 vulnerability in @fastify/multipart. A fix is available for @fastify/multipart — see the affected versions and patch details below.

Also known asCVE-2023-25576

Published

Feb 14, 2023

Updated

Nov 8, 2023

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Nov 7, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-hpp2-2cr5-pf6g.

EPSS Exploitation Probability

via FIRST.org ↗

1.5%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs74th percentile — riskier than 74% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

2 pkgs affected

How broadly this vulnerability is actually deployed: weekly install volume shows current usage, and reverse-dependency count shows how many other packages break if it stays unpatched.

581other npm packages depend on this — each one inherits the vulnerability until it's patched upstream

@fastify/multipartnpm

4.7Mdownloads / week

Description

@fastify/multipart is a Fastify plugin to parse the multipart content-type. Prior to versions 7.4.1 and 6.0.1, @fastify/multipart may experience denial of service due to a number of situations in which an unlimited number of parts are accepted. This includes the multipart body parser accepting an unlimited number of file parts, the multipart body parser accepting an unlimited number of field parts, and the multipart body parser accepting an unlimited number of empty parts as field parts. This is fixed in v7.4.1 (for Fastify v4.x) and v6.0.1 (for Fastify v3.x). There are no known workarounds.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`@fastify/multipart`	all versions	6.0.1`npm install @fastify/multipart@6.0.1`
📦npm	`@fastify/multipart`	≥ 7.0.0&&< 7.4.1	7.4.1`npm install @fastify/multipart@7.4.1`

Affected Products

1 product · 2 configurations

Application

fastify-multipartfastify

≥ 7.0.0 && < 7.4.1

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for @fastify/multipart, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update @fastify/multipart to 6.0.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-hpp2-2cr5-pf6g is resolved across your whole dependency graph.
Workarounds
Cap what an attacker can consume: apply request size, rate and timeout limits in front of the affected component, and run it with memory and CPU limits so exhaustion degrades one worker rather than the whole service.

Frequently Asked Questions

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