fix(deps): update dependency multer to v2.3.0 [security]

[renovate]

This PR contains the following updates:

Package	Change	Age	Confidence
multer	2.1.1 → 2.3.0

---

Multer vulnerable to Denial of Service via incomplete cleanup of aborted uploads

CVE-2026-5038 / GHSA-3p4h-7m6x-2hcm

More information

Details

Impact

A vulnerability in Multer allows an attacker to trigger a Denial of Service (DoS) by aborting or sending malformed multipart uploads, causing orphaned partial files to accumulate on disk when using diskStorage.

Patches

Users should upgrade to 2.2.0, 3.0.0-alpha.2 or higher

Workarounds

None

Severity

• CVSS Score: 5.3 / 10 (Medium)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L

References

• https://github.com/expressjs/multer/security/advisories/GHSA-3p4h-7m6x-2hcm
• https://nvd.nist.gov/vuln/detail/CVE-2026-5038
• https://cna.openjsf.org/security-advisories.html
• https://github.com/advisories/GHSA-3p4h-7m6x-2hcm

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Multer vulnerable to Denial of Service via deeply nested field names

CVE-2026-5079 / GHSA-72gw-mp4g-v24j

More information

Details

Impact

Multer is vulnerable to a Denial of Service (DoS) via deeply nested field names in multipart form data. The append-field dependency parses bracket notation in field names (e.g., a[b][c]) with no limit on nesting depth, allowing an attacker to force allocation of deeply nested object structures that consume CPU and memory. A single HTTP request with a crafted multipart body is sufficient to exploit this.

Patches

Users should upgrade to 2.2.0 and configure limits.fieldNestingDepth to the minimum depth their application requires.

Workarounds

Set limits.fields to a reasonable value to reduce the number of fields an attacker can send per request. This does not fully mitigate the issue but limits the impact.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/expressjs/multer/security/advisories/GHSA-72gw-mp4g-v24j
• https://nvd.nist.gov/vuln/detail/CVE-2026-5079
• https://cna.openjsf.org/security-advisories.html
• https://github.com/advisories/GHSA-72gw-mp4g-v24j

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

multer vulnerable to Denial of Service via oversized array index in field names

CVE-2026-82333 / GHSA-535w-7cp7-47q4

More information

Details

Impact

multer is vulnerable to a Denial of Service (DoS) via a crafted array index in multipart field names. The append-field dependency parses bracket notation in field names, and a large numeric index such as items[4294967294] forces allocation of a maximum-length sparse array. A following field with a non-numeric key on the same base then converts that array to an object by iterating its full length, which consumes CPU synchronously and leaves the process unable to handle other requests. A single HTTP request with a crafted multipart body is sufficient to exploit this, and it affects multer 1.x and 2.x.

Patches

Users should upgrade to 2.3.0 and configure limits.fieldArrayIndexLimit to the minimum array index their application requires.

Workarounds

None.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/expressjs/multer/security/advisories/GHSA-535w-7cp7-47q4
• https://nvd.nist.gov/vuln/detail/CVE-2026-82333
• https://github.com/expressjs/multer/pull/1438
• https://github.com/expressjs/multer/commit/73c1759fa93b87366bc6dbd7abe1b80ddff7d27c
• https://cna.openjsf.org/security-advisories.html
• https://github.com/expressjs/multer/releases/tag/v2.3.0
• https://github.com/advisories/GHSA-535w-7cp7-47q4

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

multer vulnerable to file size limit bypass via async fileFilter race condition

CVE-2026-77063 / GHSA-qvfw-j98x-7q72

More information

Details

Impact

When multer is configured with an asynchronous fileFilter, the limits.fileSize limit can be bypassed. The 'limit' event is registered inside the async fileFilter callback, so if a file exceeds limits.fileSize before that callback runs, the event is missed and the oversized upload is accepted instead of being rejected with a LIMIT_FILE_SIZE error. Applications that rely on limits.fileSize to reject oversized uploads are affected on all upload methods (.single(), .array(), .fields(), .any()). Uploads using a synchronous fileFilter are not affected.

Patches

Users should upgrade to 2.3.0.

Workarounds

Use a synchronous fileFilter, or validate the uploaded file size after the upload completes.

Severity

• CVSS Score: 3.7 / 10 (Low)
• Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:L/A:N

References

• https://github.com/expressjs/multer/security/advisories/GHSA-qvfw-j98x-7q72
• https://nvd.nist.gov/vuln/detail/CVE-2026-77063
• https://github.com/expressjs/multer/commit/ab6aeae650328cf31799dcfa4c3e116ba8faaacc
• https://cna.openjsf.org/security-advisories.html
• https://github.com/expressjs/multer/releases/tag/v2.3.0
• https://github.com/advisories/GHSA-qvfw-j98x-7q72

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

multer vulnerable to Denial of Service via crafted multipart field names

CVE-2026-77078 / GHSA-wc9g-mqfw-jrwm

More information

Details

Impact

A vulnerability in multer allows a remote, unauthenticated attacker to crash the Node.js process with a single multipart/form-data request. Two specially crafted text field names cause an uncaught RangeError: Invalid array length inside multer's field parsing, which is not routed to the application error handler and terminates the process. All applications using multer to parse multipart requests are affected.

Patches

Users should upgrade to 2.3.0.

Workarounds

None.

Severity

• CVSS Score: 7.5 / 10 (High)
• Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H

References

• https://github.com/expressjs/multer/security/advisories/GHSA-wc9g-mqfw-jrwm
• https://nvd.nist.gov/vuln/detail/CVE-2026-77078
• https://github.com/expressjs/multer/commit/87a584e8c8d4da873292635fa1d8c4d78d985b76
• https://cna.openjsf.org/security-advisories.html
• https://github.com/expressjs/multer/releases/tag/v2.3.0
• https://github.com/advisories/GHSA-wc9g-mqfw-jrwm

This data is provided by the GitHub Advisory Database (CC-BY 4.0).

---

Release Notes

expressjs/multer (multer)

v2.3.0

Compare Source

• Fix CVE-2026-77078 (GHSA-wc9g-mqfw-jrwm)
• Fix CVE-2026-77037 (GHSA-qfvm-cv95-jqjf)
• Fix CVE-2026-77063 (GHSA-qvfw-j98x-7q72)
• Fix CVE-2026-82333 (GHSA-535w-7cp7-47q4)
• Add MulterError codes INVALID_FIELD_NAME and STREAM_DESTROYED
• Add opt-in limits.fieldArrayIndexLimit to bound numeric array indexes in field names (#​1438)
• Accept files whose size is exactly limits.fileSize (#​1407)
• Preserve the caller's async context (AsyncLocalStorage) when calling next() (#​1124)
• Decode WHATWG-escaped characters (%0A, %0D, %22) in file.originalname (#​1421)
• Do not crash when fileFilter invokes its callback more than once (#​1427)
• Use a fallback message for MulterError codes without a mapping (#​1448)
• Docs: clarify preservePath and parts, use crypto.randomBytes in the DiskStorage example (#​1414, #​1430, #​1436)
• Docs: add Indonesian, Japanese and Tamil translations and refresh all translations from the current README (#​1431, #​1354, #​1462)
• Internal: run the test suite on Windows (#​1334)

v2.2.0

Compare Source

• Fix CVE-2026-5038 (GHSA-3p4h-7m6x-2hcm)
• Fix CVE-2026-5079 (GHSA-72gw-mp4g-v24j)

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

This PR was generated by Mend Renovate. View the repository job log.

[renovate]

⚠️ Artifact update problem

Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.

♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

• any of the package files in this branch needs updating, or
• the branch becomes conflicted, or
• you click the rebase/retry checkbox if found above, or
• you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:

File name: 08-node-express-uploading/package-lock.json

npm warn Unknown env config "store". This will error in a future major version of npm. See `npm help npmrc` for supported config options.
npm error code ERESOLVE
npm error ERESOLVE could not resolve
npm error
npm error While resolving: multer-storage-cloudinary@4.0.0
npm error Found: cloudinary@2.7.0
npm error node_modules/cloudinary
npm error   cloudinary@"2.7.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer cloudinary@"^1.21.0" from multer-storage-cloudinary@4.0.0
npm error node_modules/multer-storage-cloudinary
npm error   multer-storage-cloudinary@"4.0.0" from the root project
npm error
npm error Conflicting peer dependency: cloudinary@1.41.3
npm error node_modules/cloudinary
npm error   peer cloudinary@"^1.21.0" from multer-storage-cloudinary@4.0.0
npm error   node_modules/multer-storage-cloudinary
npm error     multer-storage-cloudinary@"4.0.0" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry this command with --force or --legacy-peer-deps to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /runner/cache/others/npm/_logs/2026-10-13T17_28_20_826Z-eresolve-report.txt
npm error A complete log of this run can be found in: /runner/cache/others/npm/_logs/2026-10-13T17_28_20_826Z-debug-0.log