Nicolás Pstyga@NicoPstyga
Security fix del CVE-2026-113872 gracias a @kom_256 👌
02030103
1.4K followersView on X
CVE-2026-113872
LOWCVSS 7.5 · HIGHImmediate actions
- Track advisory updates for patch or workaround availability
Recommended action window: Monitor and triage in normal cycle
NVD description
multer is a middleware for Node.js that handles multipart/form-data file uploads. In versions from 2.0.0 before 2.5.0, when multer is configured with an asynchronous fileFilter, a single request can crash the Node.js process. If the request is aborted while one file's asynchronous fileFilter is still pending, the pending callback later resumes a parsing stream that multer has already torn down, and the underlying parser emits an error on a stream that no longer has an error listener, which Node raises as an unhandled error event so the process exits. Any application using multer with an asynchronous fileFilter is affected regardless of storage engine, while uploads using a synchronous fileFilter are not affected. The issue is fixed in multer 2.5.0, and users should upgrade to 2.5.0 or later. As a workaround, use a synchronous fileFilter.
0.0/ 10 priority
Sources & remediation
Other references
Weakness type (CWE)
CWE-248CWE-404
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE
Deep dive
Full discourse2 posts
Upwind Security MDR@UpwindMDR🚨HIGH - Multer DoS via async fileFilter abort race (CVE-2026-113872) In multer’s multipart parser, an async fileFilter(req, file, cb) can outlive an aborted request; when the pending callback resumes the stream after teardown, it triggers an unhandled 'error' event and crashes the Node.js process. Synchronous fileFilter configs are not affected. 👉Affected: multer >= 2.0.0 < 2.5.0 | Upgrade to 2.5.0
0000072359 followersView on X