Repository navigation
[Snyk] Security upgrade express from 5.1.0 to 5.2.0 - #74
nickbaxter18 wants to merge 1 commit into
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-EXPRESS-14157151
|
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| "ajv": "^8.17.1", | ||
| "ajv-formats": "^3.0.1", | ||
| "dotenv": "^17.2.2", | ||
| "express": "^5.1.0", | ||
| "express": "^5.2.0", |
There was a problem hiding this comment.
Express upgrade not reflected in pnpm lockfile
The dependency is bumped to ^5.2.0, but pnpm-lock.yaml still resolves express@5.1.0 (e.g., lines 3349 and 9846), and the repo declares pnpm@9.12.0 as the package manager. Any install using the lockfile will keep 5.1.0, so the Prototype Pollution fix this commit targets will not ship. Please regenerate the pnpm lockfile so Express 5.2.0 is actually installed.
Useful? React with 👍 / 👎.



Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-EXPRESS-14157151
Important
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:
🦉 Prototype Pollution
Note
Updates
expressinpackage.jsonfrom^5.1.0to^5.2.0.Written by Cursor Bugbot for commit 9a4d787. This will update automatically on new commits. Configure here.