Skip to content

[Snyk] Security upgrade multer from 2.2.0 to 2.5.0 - #1259

Open
tagyoureit wants to merge 1 commit into
masterfrom
snyk-fix-854c2256952df726ffbbe7c280bc4647
Open

tagyoureit wants to merge 1 commit into
masterfrom
snyk-fix-854c2256952df726ffbbe7c280bc4647

Conversation

@tagyoureit

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Uncaught Exception
SNYK-JS-MULTER-21431602

Breaking Change Risk

Merge Risk: Medium

Notice: This assessment is enhanced by AI.


Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.
  • This PR was automatically created by Snyk using the credentials of a real user.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.

For more information:
🧐 View latest project report
📜 Customise PR templates
🛠 Adjust project settings
📚 Read about Snyk's upgrade logic


Learn how to fix vulnerabilities with free interactive lessons:

🦉 Uncaught Exception

@tagyoureit

Copy link
Copy Markdown
Owner Author

Merge Risk: Medium

This minor version upgrade for multer contains numerous security fixes and several behavioral changes that could impact applications relying on previous workarounds.

Behavioral Changes & Potential Breaks:

  • Field Name Decoding: Versions 2.3.0 and 2.4.0 introduced decoding for escaped characters in file.originalname and field names. If your code implemented workarounds to handle escaped names (e.g., matching %0A), it must be updated to use the real, decoded names.
  • Part Limits: The LIMIT_PART_COUNT behavior was corrected. It now fires only when the limit is exceeded, not when it is met. If you previously set the limit one higher as a workaround, you can now remove it.
  • Filtering: Files that are skipped by fileFilter no longer count towards the maxCount limit.

Recommendation: Review the changelog to assess the impact of these behavioral changes, especially if you have implemented custom workarounds for field name encoding or request limits. The upgrade is recommended for the included security patches.

Source: GitHub Changelog

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants