Skip to content

[Snyk] Upgrade express from 4.19.2 to 4.22.1 #92

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

Jump to bottom
Open
Danilqa wants to merge 1 commit into
base: main
Choose a base branch
from
Open

[Snyk] Upgrade express from 4.19.2 to 4.22.1 #92

Danilqa wants to merge 1 commit into from

Conversation

@Danilqa
Copy link
Owner

@Danilqa Danilqa commented Dec 29, 2025 •
edited by cursor bot
Loading

snyk-top-banner

Snyk has created this PR to upgrade express from 4.19.2 to 4.22.1.

ℹ️ Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

  • The recommended version is 6 versions ahead of your current version.

  • The recommended version was released a month ago.

Issues fixed by the recommended upgrade:

Issue Score Exploit Maturity
high severity Asymmetric Resource Consumption (Amplification)
SNYK-JS-BODYPARSER-7926860		 624 No Known Exploit
medium severity Cross-site Scripting (XSS)
SNYK-JS-COOKIE-8163060		 624 No Known Exploit
medium severity Cross-site Scripting
SNYK-JS-EXPRESS-7926867		 624 No Known Exploit
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-7925106		 624 Proof of Concept
medium severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-PATHTOREGEXP-8482416		 624 Proof of Concept
low severity Cross-site Scripting
SNYK-JS-SEND-7926862		 624 No Known Exploit
low severity Cross-site Scripting
SNYK-JS-SERVESTATIC-7926865		 624 No Known Exploit
Release notes
Package name: express from express GitHub release notes

Important

  • Check the changes in this PR to ensure they won't cause issues with your project.
  • This PR was automatically created by Snyk using the credentials of a real user.
  • Max score is 1000. Note that the real score may have changed since the PR was raised.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.

For more information:

Note

Updates dependency version only.

  • Upgrade express in examples/express/package.json from 4.19.2 to 4.22.1

Written by Cursor Bugbot for commit c24c352. This will update automatically on new commits. Configure here.

@snyk-bot
fix: upgrade express from 4.19.2 to 4.22.1
c24c352 
Snyk has created this PR to upgrade express from 4.19.2 to 4.22.1.

See this package in npm:
express

See this project in Snyk:
https://app.snyk.io/org/danilqa/project/eb967200-65f0-411c-a10e-b3dd14e10c25?utm_source=github&utm_medium=referral&page=upgrade-pr
@vercel
Copy link

vercel bot commented Dec 29, 2025 •
edited
Loading

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
node-file-router Ready Ready Preview, Comment Dec 29, 2025 9:55am

cursor[bot]
cursor bot reviewed Dec 29, 2025
View reviewed changes
examples/express/package.json
"dependencies": {
"node-file-router": "workspace:../../dist",
"express": "4.19.2"
"express": "4.22.1"
Copy link

@cursor cursor bot Dec 29, 2025

Choose a reason for hiding this comment

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

Lockfile not updated to match new dependency version

The package.json was updated to require express 4.22.1, but the pnpm-lock.yaml file wasn't regenerated and still references version 4.19.2. This creates an inconsistency that could cause CI failures with --frozen-lockfile, and more critically, the security vulnerabilities this PR aims to fix may not actually be resolved if the old version gets installed from the stale lockfile. The lockfile needs to be regenerated to complete this dependency upgrade.

Fix in Cursor Fix in Web

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@cursor cursor[bot] cursor[bot] left review comments

At least 1 approving review is required to merge this pull request.

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

3 participants

@Danilqa @snyk-bot