How severe is GHSA-qfvm-cv95-jqjf?

GHSA-qfvm-cv95-jqjf has a CVSS score of 7.5/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-qfvm-cv95-jqjf?

GHSA-qfvm-cv95-jqjf affects the following packages: multer (npm). Ecosystems affected: npm.

How do I fix GHSA-qfvm-cv95-jqjf?

Update multer to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qfvm-cv95-jqjf is resolved across your whole dependency graph.

How do I detect GHSA-qfvm-cv95-jqjf in my npm dependencies?

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

How do I mitigate GHSA-qfvm-cv95-jqjf 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-qfvm-cv95-jqjf actively exploited in the wild?

No public exploit code has been indexed for GHSA-qfvm-cv95-jqjf 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-qfvm-cv95-jqjf?

GHSA-qfvm-cv95-jqjf has an EPSS (Exploit Prediction Scoring System) score of 0.3%, placing it in the 26th 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-qfvm-cv95-jqjf?

GHSA-qfvm-cv95-jqjf is classified as Uncontrolled Resource Consumption (CWE-400), CWE-459 (CWE-459). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-qfvm-cv95-jqjf published, and has it been updated?

GHSA-qfvm-cv95-jqjf was published on September 8, 2026 and was last updated on September 8, 2026. 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

multer vulnerable to Denial of Service via file descriptor leak on aborted uploadsGHSA-qfvm-cv95-jqjf

HIGHFix: expressjs/multer@eef7444

GHSA-qfvm-cv95-jqjf is a high-severity (CVSS 7.5) Uncontrolled Resource Consumption vulnerability in multer. A fix is available for multer — see the affected versions and patch details below.

Also known asCVE-2026-77037

Published

Sep 8, 2026

Updated

Sep 8, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 12, 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-qfvm-cv95-jqjf.

EPSS Exploitation Probability

via FIRST.org ↗

0.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs26th percentile — riskier than 26% of all scored CVEsHighest risk

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

How urgent is this, really

GHSA-qfvm-cv95-jqjf by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,987 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

1 pkg 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.

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

multernpm

23.0Mdownloads / week

Description

multer is a middleware for handling multipart/form-data in Node.js. In version 2.2.0, when a disk-backed upload is aborted or truncated before the write stream finishes, multer's disk storage engine removes the visible file but does not close the underlying write file descriptor, leaving a deleted but still open descriptor. A remote attacker able to reach an upload route using the built-in disk storage can send repeated aborted or malformed multipart uploads, each one leaking a file descriptor and retaining disk blocks until the process exits, which can exhaust resources and cause a denial of service. The issue is fixed in multer 2.3.0, which closes the destination write stream on abnormal source termination and defers cleanup until the stream has closed. Upgrade to multer 2.3.0 to remediate.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
📦npm	`multer`	≥ 2.2.0&&< 2.3.0	2.3.0`npm install multer@2.3.0`

Affected Products

1 product · 1 configurations

Application

multerexpressjs

1 version

2.2.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for multer, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update multer to 2.3.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-qfvm-cv95-jqjf 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.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

A file descriptor leak vulnerability was found in multer, a Node.js middleware for handling multipart/form-data. When using multer's built-in diskStorage engine, aborted or truncated uploads cause the disk storage engine to remove the visible file but fail to close the underlying write file descriptor. A remote…

Workaround published by Red Hat

Upgrade to multer 2.3.0 or later, which properly closes the destination write stream on abnormal source termination and defers cleanup until the stream has closed.

Source: Red Hat security advisory for GHSA-qfvm-cv95-jqjf (CC BY 4.0)

Product	Fixed in	Advisory
Red Hat Developer Hub 1.10	`rhdh/red-hat-developer-hub-backstage-plugin-orchestrator-backend:1791251282`	RHSA-2026:76788
Red Hat Developer Hub 1.10	`rhdh/rhdh-hub-rhel9:1791311495`	RHSA-2026:79088

Frequently Asked Questions

### Impact A vulnerability in multer `2.2.0` allows an attacker to trigger a Denial of Service (DoS) by aborting or truncating multipart uploads. When using `diskStorage`, the destination write stream is not closed if the upload is aborted before it finishes, so each failed request leaks an open file descriptor and retains its disk blocks until the process exits. Repeated failed uploads can exhaust the available file descriptors. All applications using multer's disk storage are affected. ### Patches Users should upgrade to `2.3.0`. ### Workarounds None.