[Snyk] Security upgrade express from 4.17.1 to 4.22.0

[prma85]

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_14/package.json

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-QS-14724253	828

---

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

---

Note

Dependency upgrade

• Updates express in resources/solution/node.js/ex_14/package.json from ^4.17.1 to ^4.22.0.
• Security-driven update per Snyk to remediate a vulnerability.

^{Written by Cursor Bugbot for commit 7f7dbfd. This will update automatically on new commits. Configure here.}

[cursor]

This is the final PR Bugbot will review for you during this billing cycle

Your free Bugbot reviews will reset on January 7

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

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

[cursor]

Lock file not updated, vulnerability remains for npm ci

The package.json is updated to Express 4.22.0, but the existing package-lock.json still pins Express 4.17.1 and the vulnerable qs version 6.7.0. When npm ci is used (common in CI/CD pipelines), the lock file takes precedence, causing the old vulnerable version to be installed. The security vulnerability this PR aims to fix (SNYK-JS-QS-14724253) will remain present unless the lock file is also regenerated and committed.