When multer is configured with an asynchronous fileFilter, a single request can crash the Node.js process. If a request is aborted (for example when one file is rejected) while another file's async fileFilter is still pending, the pending callback later resumes a parsing stream that multer has already torn down. busboy then emits an error on a stream that no longer has an error listener, which Node raises as an unhandled 'error' event, and the process exits. A single unauthenticated request is enough, so any application using multer with an asynchronous fileFilter is affected, regardless of storage engine. Uploads using a synchronous fileFilter are not affected.
Users should upgrade to multer 2.5.0 or later.
Use a synchronous fileFilter.
{
"cwe_ids": [
"CWE-248",
"CWE-404"
],
"github_reviewed": true,
"github_reviewed_at": "2026-10-23T22:08:22Z",
"nvd_published_at": "2026-10-22T15:17:05Z",
"severity": "HIGH"
}