# multer vulnerable to Denial of Service via a pending asynchronous fileFilter after request teardown

Advisory record · `GHSA-q7qp-rjg7-q26m`

- **Identifiers:** `GHSA-q7qp-rjg7-q26m` · `CVE-2026-113872`
- **State:** Confirmed
- **Severity:** CVSS 7.5 High
- **Critical:** No
- **Weakness (CWE):** [CWE-248](https://cwe.mitre.org/data/definitions/248.html) · [CWE-404](https://cwe.mitre.org/data/definitions/404.html)
- **Tags:** [Denial of service](https://agentprime.io/advisories/tag/dos.md) · [CWE-248](https://agentprime.io/advisories/tag/cwe-248.md)
- **Published:** 23 Oct 2026
- **Updated:** 23 Oct 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 23 Oct 2026, 22:08 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `multer` (npm): affected `>=2.0.0, <2.5.0`; fixed in `2.5.0`

## Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

> The multer npm package, versions from 2.0.0 before 2.5.0, is vulnerable when configured with an asynchronous fileFilter. A single unauthenticated upload request can crash the Node.js process, because a pending async filter callback resumes a parsing stream after the request has been torn down, producing an unhandled error event. Upgrade to multer 2.5.0 or later; the source notes that using a synchronous fileFilter avoids the issue as a workaround.

Written 31 Oct 2026.

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 7.5 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`, from CNA (openjs)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0044, the 38th percentile, on 5 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 13:33 UTC: First seen by agentprime
- 31 Oct 2026, 13:33 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-q7qp-rjg7-q26m)

## Sources

- [GitHub Advisory Database: GHSA-q7qp-rjg7-q26m](https://github.com/advisories/GHSA-q7qp-rjg7-q26m)
- [OSV: GHSA-q7qp-rjg7-q26m](https://osv.dev/vulnerability/GHSA-q7qp-rjg7-q26m)
- <https://github.com/expressjs/multer/security/advisories/GHSA-q7qp-rjg7-q26m>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-113872>
- <https://github.com/expressjs/multer/commit/80a2d9df1dfd63b5fab631b8b9966164ed647adf>
- <https://cna.openjsf.org/security-advisories.html>
- <https://github.com/expressjs/multer>
- <https://github.com/expressjs/multer/releases/tag/v2.5.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-q7qp-rjg7-q26m>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-q7qp-rjg7-q26m/>. Everything for agents: <https://agentprime.io/llms.txt>.