Quick answers
- Is CVE-2026-77078 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-77078 being exploited in the wild.
- How severe is CVE-2026-77078?
- High severity, with a CVSS score of 7.5, published 28 August 2026.
- Which products and versions are affected?
- multer (npm) SEMVER:introduced=0,fixed=2.3.0.
- Is there a fix for CVE-2026-77078?
- Yes. multer (npm): upgrade to 2.3.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-77078 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-77078?
- Check whether you run multer (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- multer (npm): upgrade to 2.3.0 or later
npm install multer@2.3.0
Technical details
An uncaught exception (CWE-248) in multer's multipart field parsing logic allows two specially crafted text field names to trigger a RangeError: Invalid array length. The vulnerability exists in the field parsing component which is reached during normal multipart/form-data request processing. No authentication or user interaction is required; the attack vector is network-based and exploitable from any remote client. When triggered, the exception is not caught by multer's error handler and propagates uncaught, terminating the Node.js process. The patch is available in version 2.3.0 and later.
Affected products
- Express.js Foundation multer < 2.3.0
Identifiers
- CVE-2026-77078
- GHSA-wc9g-mqfw-jrwm
Timeline
- 2026-08-28: disclosed
- 2026-09-08: patched: Version 2.3.0 released