You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This update includes minor version bumps for body-parser and express, introducing security fixes and some behavioral changes that warrant review.
body-parser 1.20.1 → 1.20.9
This is a patch upgrade. Key changes include:
1.20.3: The default depth for parsing URL-encoded data is now 32 (previously Infinity). This could affect applications processing deeply nested objects in POST requests.
1.20.6: Invalid limit option values (e.g., unparseable strings) now throw an error instead of being ignored. This improves security by ensuring size limits are enforced.
Other versions include dependency updates and minor bug fixes.
express 4.18.2 → 4.22.0
This is a minor version upgrade within the same major version. The changes are primarily focused on security and dependency updates:
4.19.0 / 4.19.1: Fixed an open redirect vulnerability.
4.20.0: Fixed an XSS vulnerability.
4.21.1 / 4.21.2: Updated dependencies (cookie, path-to-regexp) to address vulnerabilities.
4.22.0: This version initially included a change to the query parser that was later reverted in 4.22.1 because it was an erroneous breaking change.
Recommendation:
While these upgrades do not contain major API removals, the change in body-parser's default parsing depth and stricter limit handling could impact specific use cases. It is recommended to verify that your application is not affected by these changes, especially if you handle complex, nested URL-encoded data or rely on the previous lenient behavior of the limit option. The express updates are primarily for security and should be safe to apply.
Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You have signed the CLA already but the status is still pending? Let us recheck it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-BODYPARSER-21431495
Breaking Change Risk
Important
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