Skip to content

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

Open
alejandrosuarez wants to merge 2 commits into
mainfrom
snyk-fix-9ca730a42fabcd932ace435b61036ef5
Open

[Snyk] Security upgrade express from 4.17.1 to 4.22.0#37
alejandrosuarez wants to merge 2 commits into
mainfrom
snyk-fix-9ca730a42fabcd932ace435b61036ef5

Conversation

@alejandrosuarez
Copy link
Copy Markdown
Owner

@alejandrosuarez alejandrosuarez commented Feb 15, 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):

  • package.json
  • 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


Summary by cubic

Upgraded Express to 4.22.0 to pull in a patched qs and newer HTTP middleware, resolving a security issue. Only package.json and package-lock.json were updated.

  • Bug Fixes

    • Resolved Allocation of Resources Without Limits or Throttling (SNYK-JS-QS-15268416) via qs 6.14.x included with Express 4.22.0.
  • Dependencies

    • Bumped Express from ^4.16.3/4.17.1 to ^4.22.0; notable transitive updates: body-parser 1.20.4, qs 6.14.2, finalhandler 1.3.2, send 0.19.2, serve-static 1.16.3, cookie 0.7.2, http-errors 2.0.1, encodeurl 2.0.0, on-finished 2.4.1, proxy-addr 2.0.7, statuses 2.0.2.
    • No application code changes.

Written for commit 1f2a327. Summary will update on new commits.

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @alejandrosuarez, I'm Gemini Code Assist1! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request focuses on enhancing the project's security posture by performing a critical upgrade of the express framework and its associated packages. This update mitigates a known vulnerability, ensuring the application remains robust against potential resource allocation issues.

Highlights

  • Security Upgrade: Upgraded the express package from version 4.17.1 to 4.22.0 to address a security vulnerability related to 'Allocation of Resources Without Limits or Throttling' (SNYK-JS-QS-15268416).
  • Dependency Updates: Updated numerous transitive dependencies in package-lock.json to their latest versions, ensuring a more secure and up-to-date dependency tree.
Changelog
  • package-lock.json
    • Updated express to version 4.22.0.
    • Updated accepts from 1.3.7 to 1.3.8.
    • Updated body-parser from 1.19.0 to 1.20.4.
    • Updated bytes from 3.1.0 to 3.1.2.
    • Added new dependencies call-bind-apply-helpers, call-bound, dunder-proto, es-define-property, es-errors, es-object-atoms, get-proto, gopd, hasown, math-intrinsics, side-channel-list, side-channel-map, and side-channel-weakmap.
    • Updated content-disposition from 0.5.3 to 0.5.4.
    • Updated content-type from 1.0.4 to 1.0.5.
    • Updated cookie from 0.4.0 to 0.7.2.
    • Updated depd from 1.1.2 to 2.0.0.
    • Updated destroy from 1.0.4 to 1.2.0.
    • Updated ee-first to include license information.
    • Updated encodeurl from 1.0.2 to 2.0.0.
    • Updated escape-html to include license information.
    • Updated etag to include license information.
    • Updated finalhandler from 1.1.2 to 1.3.2.
    • Updated forwarded from 0.1.2 to 0.2.0.
    • Updated fresh to include license information.
    • Updated function-bind from 1.1.1 to 1.1.2.
    • Updated get-intrinsic from 1.1.1 to 1.3.0.
    • Updated has-symbols from 1.0.2 to 1.1.0.
    • Updated http-errors from 1.7.2 to 2.0.1.
    • Updated iconv-lite to include license information.
    • Updated inherits from 2.0.3 to 2.0.4.
    • Updated ipaddr.js to include license information.
    • Updated media-typer to include license information.
    • Updated merge-descriptors from 1.0.1 to 1.0.3.
    • Updated mime-db from 1.45.0 to 1.52.0.
    • Updated mime-types from 2.1.28 to 2.1.35.
    • Updated negotiator from 0.6.2 to 0.6.3.
    • Updated object-inspect from 1.11.0 to 1.13.4.
    • Updated on-finished from 2.3.0 to 2.4.1.
    • Updated parseurl to include license information.
    • Updated path-to-regexp from 0.1.7 to 0.1.12.
    • Updated proxy-addr from 2.0.6 to 2.0.7.
    • Updated qs from 6.7.0 to 6.14.2.
    • Updated raw-body from 2.4.0 to 2.5.3.
    • Updated range-parser to include license information.
    • Updated safe-buffer to include license information and funding URLs.
    • Updated send from 0.17.1 to 0.19.2.
    • Updated serve-static from 1.14.1 to 1.16.3.
    • Updated setprototypeof from 1.1.1 to 1.2.0.
    • Updated side-channel from 1.0.4 to 1.1.0.
    • Updated statuses from 1.5.0 to 2.0.2.
    • Updated toidentifier from 1.0.0 to 1.0.1.
    • Updated unpipe to include license information.
  • package.json
    • Updated express dependency from ^4.16.3 to ^4.22.0.
Activity
  • Snyk automatically created this pull request to fix 1 identified vulnerability in the npm dependencies.
  • The vulnerability addressed is 'Allocation of Resources Without Limits or Throttling' (SNYK-JS-QS-15268416) with a score of 708.
Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature Command Description
Code Review /gemini review Performs a code review for the current pull request in its current state.
Pull Request Summary /gemini summary Provides a summary of the current pull request in its current state.
Comment @gemini-code-assist Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help /gemini help Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

  1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution.

@socket-security
Copy link
Copy Markdown

socket-security Bot commented Feb 15, 2026

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednpm/​express@​4.17.1 ⏵ 4.22.097100 +310087100

View full report

Copy link
Copy Markdown

@cubic-dev-ai cubic-dev-ai Bot left a comment

Choose a reason for hiding this comment

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

No issues found across 2 files

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Choose a reason for hiding this comment

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

Code Review

This pull request, automatically generated by Snyk, aims to upgrade express to fix a security vulnerability. However, it attempts to upgrade to version 4.22.0, which does not exist in the public npm registry. This will cause the build to fail.

I've left suggestions to update express to the latest stable version, 4.19.2, in package.json and to regenerate package-lock.json. This should resolve the issue and fix the vulnerability.

Comment thread package.json
"cli-table": "0.3.5",
"colors": "1.4.0",
"express": "^4.16.3",
"express": "^4.22.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

The target version 4.22.0 for express does not exist in the public npm registry, which will cause dependency installation to fail. I suggest updating to the latest stable version, 4.19.2, which also includes the fix for the security vulnerability.

Suggested change
"express": "^4.22.0",
"express": "^4.19.2",

Comment thread package-lock.json
"version": "4.17.1",
"resolved": "https://registry.npmjs.org/express/-/express-4.17.1.tgz",
"integrity": "sha512-mHJ9O79RqluphRrcw2X/GTh3k9tVv8YcoyY4Kkh4WDMUYKRZUq0h1o0w2rrrxBqM7VoeUVqgb27xlEMXTnYt4g==",
"version": "4.22.0",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

critical

This lock file is generated for express version 4.22.0, which is not a valid version available on npm. After correcting the version in package.json, please regenerate package-lock.json by running npm install.

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