CVE-2026-77078 is an uncaught-exception vulnerability affecting Multer versions before 2.3.0, a Node.js middleware for processing multipart/form-data. Two specially crafted text-field names cause the append-field dependency to create a maximum-length sparse JavaScript array and then attempt to append another element. The resulting RangeError, indicating an invalid array length, escapes Multer's asynchronous field-processing flow and terminates the Node.js process. A small, remotely submitted multipart request can therefore cause denial of service. Multer 2.3.0 catches field-processing exceptions and returns an INVALID_FIELD_NAME middleware error instead of allowing the process to crash.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This 12-file TypeScript repository is an operational local proof of concept for CVE-2026-77078, an unauthenticated denial-of-service condition in Multer's multipart field-name processing. index.ts is the exploit client: it builds a raw multipart request with a maximum numeric array index followed by an append-style field name and POSTs it to 127.0.0.1:3000/upload. The src/ directory is a minimal NestJS target application: main.ts starts the app, app.module.ts loads UploadModule, and upload.controller.ts exposes POST /upload using NestJS FileInterceptor, a wrapper around Multer. The supplied package-lock resolves @nestjs/platform-express 11.2.5 and multer 2.2.0, an affected release. English and Russian Markdown files document the vulnerability, expected crash behavior, detection signals, and upgrade guidance to Multer 2.3.0 or later. The code contains no shell, persistence, data-exfiltration, or remote-code-execution payload; its sole capability is triggering process-level availability loss on an affected multipart endpoint.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
7 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A remotely triggerable denial-of-service vulnerability in multer, a Node.js multipart/form-data middleware. Crafted field names create a maximum-length sparse array and then push beyond its limit, triggering an exception in the append-field dependency that multer does not catch. The Node.js process terminates. The listed CVSS v3 base score is 7.5, with no authentication or user interaction required. Upgrade to multer 2.3.0 or later.
A denial-of-service vulnerability in the npm multer package. Crafted multipart field names trigger an uncaught RangeError during field parsing, allowing a remote unauthenticated attacker to terminate the Node.js process with one request.
A high-severity unauthenticated remote denial-of-service vulnerability in Multer prior to 2.3.0. Crafted multipart field names can force an invalid JavaScript array-length operation, producing an uncaught RangeError and terminating the Node.js process.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.