Skip to content

[Snyk] Fix for 1 vulnerabilities - #629

Open
caniszczyk wants to merge 1 commit into
masterfrom
snyk-fix-5eb7fba81e0abff481c1e8a6dcac64e8
Open

caniszczyk wants to merge 1 commit into
masterfrom
snyk-fix-5eb7fba81e0abff481c1e8a6dcac64e8

Conversation

@caniszczyk

Copy link
Copy Markdown

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
⚠️ Warning
Failed to update the package-lock.json, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Uncaught Exception
SNYK-JS-QS-20943482
  803  

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

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-QS-20943482
@caniszczyk

Copy link
Copy Markdown
Author

Merge Risk: Medium

This upgrade contains minor version bumps for body-parser and express. The body-parser update introduces behavioral changes that present a medium risk, while the express update is low risk.

body-parser@1.20.1 → 1.20.8

Risk: Medium

This update introduces stricter validation and new defaults that could be breaking in specific scenarios:

  • Default URL-encoded Parse Depth: In version 1.20.3, the default depth for parsing URL-encoded data was changed from Infinity to 32. Applications that process deeply nested objects in URL-encoded request bodies may encounter issues.
  • Stricter limit Option: As of version 1.20.6, invalid values for the limit option (e.g., unparseable strings) will now throw an error instead of being silently ignored. This was part of a security fix.

Recommendation:

  • Verify if your application handles deeply nested URL-encoded data.
  • Ensure that any limit option passed to body-parser is a valid value (e.g., a number or a string like '100kb').

express@4.18.2 → 4.22.3

Risk: Low

This is a minor update within the same major version, consisting primarily of security patches and bug fixes. It includes fixes for several vulnerabilities, such as an open redirect issue. A potentially breaking change to the query parser was introduced in version 4.22.0 but was reverted in 4.22.1, so it is not present in the target version 4.22.3.

Source: Package changelogs and release notes.

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

@CLAassistant

Copy link
Copy Markdown

CLA assistant check
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.

@mergeable

mergeable Bot commented Oct 15, 2026

Copy link
Copy Markdown

Thanks for creating a pull request! A maintainer will review your changes shortly. Please don't be discouraged if it takes a while.

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.

3 participants