Bug 2542092 - CVE-2026-82333 mozjs140: Multer: Denial of Service via oversized array index in field names [fedora-all]
Summary: CVE-2026-82333 mozjs140: Multer: Denial of Service via oversized array index ...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: mozjs140
Version: rawhide
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
Assignee: František Zatloukal
QA Contact:
URL:
Whiteboard: {"flaws": ["41e35b1b-34d3-4188-9c72-8...
Depends On:
Blocks: CVE-2026-82333
TreeView+ depends on / blocked
 
Reported: 2026-09-27 14:30 UTC by nlevinki
Modified: 2026-10-05 21:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2026-10-05 21:40:49 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description nlevinki 2026-09-27 14:30:05 UTC
Disclaimer: Community trackers are created by Red Hat Product Security team on a best effort basis. Package maintainers are required to ascertain if the flaw indeed affects their package, before starting the update process.

multer is a middleware for handling multipart/form-data in Node.js. A small multipart request with two specially crafted text field names can make multer's field parser synchronously iterate a maximum-length sparse array, blocking the event loop so the process cannot handle other requests. A large numeric array index in the first field allocates a maximum-length sparse array, and a second field with a non-numeric key then triggers a full-length iteration inside the append-field dependency. All versions before 2.3.0 are affected, and this is a remotely triggerable denial of service. multer 2.3.0 adds an opt-in fieldArrayIndexLimit option that rejects oversized array indexes. Upgrade to multer 2.3.0 and set limits.fieldArrayIndexLimit to the largest array index your application needs to remediate.

Comment 1 František Zatloukal 2026-10-05 21:40:49 UTC
Closing CVE bug as not relevant to the mozjs package, and there is sadly no option to opt out from these reports :( .


Note You need to log in before you can comment on or make changes to this bug.