Skip to content

[Snyk] Security upgrade express from 4.17.1 to 4.22.0#237

Open
prma85 wants to merge 1 commit intomasterfrom
snyk-fix-bad4ba8b6c9834bc6aac5d545083d0d4
Open

[Snyk] Security upgrade express from 4.17.1 to 4.22.0#237
prma85 wants to merge 1 commit intomasterfrom
snyk-fix-bad4ba8b6c9834bc6aac5d545083d0d4

Conversation

@prma85
Copy link
Owner

@prma85 prma85 commented Feb 16, 2026

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):

  • resources/solution/node.js/ex_11/package.json
  • resources/solution/node.js/ex_11/package-lock.json

Vulnerabilities that will be fixed with an upgrade:

Issue Score
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  708  

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

…on/node.js/ex_11/package-lock.json to reduce vulnerabilities

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

cursor bot commented Feb 16, 2026

You have run out of free Bugbot PR reviews for this billing cycle. This will reset on March 7.

To receive reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

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

Comments