Skip to content

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

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
prma85 wants to merge 1 commit into
base: master
Choose a base branch
from
Open

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

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion resources/solution/node.js/ex_14/package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,6 @@
"author": "",
"license": "ISC",
"dependencies": {
"express": "^4.17.1"
"express": "^4.22.0"
Copy link

@cursor cursor bot Dec 31, 2025

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

Fix in Cursor Fix in Web

}
}