Skip to content

Conversation

@snyk-io
Copy link

@snyk-io snyk-io bot commented Dec 31, 2025

snyk-top-banner

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

Snyk changed the following file(s):

  • payment-components/vanilla-js/apps/server/package.json
⚠️ Warning
Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-14724253
  710  

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:

🦉 Allocation of Resources Without Limits or Throttling

… vulnerabilities

The following vulnerabilities are fixed with an upgrade:
- https://snyk.io/vuln/SNYK-JS-QS-14724253
@snyk-io
Copy link
Author

snyk-io bot commented Dec 31, 2025

Merge Risk: Low

These upgrades are minor and patch versions and should not introduce breaking changes. The express update includes a minor, unintended breaking change that was reverted in a subsequent patch, but is present in this version.

  • express@4.21.2 → 4.22.0 (low): This minor update includes an accidental breaking change related to the query parser which was reverted in 4.22.1. It also makes method functions error if no path is provided.
  • body-parser@1.20.3 → 1.20.4 (low): This is a patch release with only dependency updates and no functional changes.

Recommendation: These upgrades are likely safe, but it is recommended to validate application behavior, especially around query parameter parsing, before merging.

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

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.

1 participant