Skip to content

Fix multipart runtime advisories #5

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
LQ458 merged 1 commit into from
Jul 23, 2026
Merged

Fix multipart runtime advisories #5

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 3 additions & 0 deletions CHANGELOG.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,9 @@ contains no release tags from which to reconstruct earlier version sections.
remain valid `srcset` candidates instead of falling back to the largest
image.
- Removed an unreferenced duplicate video-modal component.
- Upgraded Multer from the deprecated 1.x line to 2.2.0 after four direct
high-severity runtime advisories were identified, retaining the existing
upload validation and cleanup contracts.

## [3.0.0] - 2026-07-23

Expand Down
2 changes: 1 addition & 1 deletion client/package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

14 changes: 7 additions & 7 deletions docs/operations/dependency-status.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -26,7 +26,7 @@ npm --prefix client audit --json --registry=https://registry.npmjs.org
npm --prefix client audit --omit=dev --json --registry=https://registry.npmjs.org
```

The root lockfile reported 283 total dependency entries, including 218
The root lockfile reported 275 total dependency entries, including 210
production entries. The client lockfile reported 1,587 total entries,
including 109 production entries. These are npm's dependency metadata counts,
not counts of directly declared packages.
Expand All @@ -45,12 +45,12 @@ expected to require a deliberate frontend build-system migration rather than a
forced lockfile rewrite. No `npm audit fix --force` or other major automatic
upgrade was run.

A clean root install also emits Multer's upstream deprecation notice for the
current `1.4.5-lts.1` release, even though npm's current production advisory
query reports zero findings. Moving the multipart boundary to Multer 2 is a
separate compatibility change: it should be paired with upload validation,
failure-cleanup, size-limit, and rollback checks rather than hidden inside a
lockfile refresh.
GitHub Dependabot subsequently identified four direct high-severity runtime
advisories affecting the previous Multer 1.x range. The root dependency is now
pinned to Multer `2.2.0`, the first release covering all four advisory ranges.
The upgrade retains the existing storage, field, count, type, and size limits;
the multipart characterization checks exercise authentication, decoded-image
rejection, path safety, missing-record cleanup, and error responses.

## Policy and follow-up

Expand Down
121 changes: 30 additions & 91 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,7 +48,7 @@
"jsonwebtoken": "^9.0.3",
"moment-timezone": "^0.5.46",
"mongoose": "^8.24.1",
"multer": "1.4.5-lts.1",
"multer": "2.2.0",
"primeflex": "^3.3.1",
"primeicons": "^7.0.0",
"primereact": "^10.8.4",
Expand Down