Skip to content

[Snyk] Fix for 3 vulnerabilities#32

Open
npv2k1 wants to merge 1 commit intomasterfrom
snyk-fix-a328f7faeefc08b5d4c8cda28d3d2c69
Open

[Snyk] Fix for 3 vulnerabilities#32
npv2k1 wants to merge 1 commit intomasterfrom
snyk-fix-a328f7faeefc08b5d4c8cda28d3d2c69

Conversation

@npv2k1
Copy link
Member

@npv2k1 npv2k1 commented Feb 16, 2026

snyk-top-banner

Snyk has created this PR to fix 3 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

  • package.json
  • pnpm-lock.yaml

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-APOLLOSERVER-15208673
  721  
medium severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-15268416
  708  
medium severity Prototype Pollution
SNYK-JS-LODASH-15053838
  559  

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:

🦉 Regular Expression Denial of Service (ReDoS)
🦉 Prototype Pollution
🦉 Allocation of Resources Without Limits or Throttling

@sonarqubecloud
Copy link

@gemini-code-assist
Copy link

Summary of Changes

Hello @npv2k1, 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, automatically generated by Snyk, focuses on enhancing the project's security posture by resolving three critical vulnerabilities. It involves updating several core and transitive dependencies to their patched versions, ensuring the application is protected against known security risks and maintaining the integrity of the dependency tree.

Highlights

  • Security Vulnerability Fixes: Addressed three identified vulnerabilities: a high-severity Regular Expression Denial of Service (ReDoS), a medium-severity Allocation of Resources Without Limits or Throttling, and a medium-severity Prototype Pollution.
  • Dependency Upgrades: Upgraded several key dependencies including @apollo/server from 4.9.3 to 5.4.0, @nestjs/apollo from 12.0.7 to 13.0.0, @nestjs/platform-express from 10.4.2 to 10.4.22, @nestjs/swagger from 6.3.0 to 11.2.6, and express from 4.18.2 to 4.22.0.
  • Lockfile Synchronization: Updated pnpm-lock.yaml to reflect the new dependency versions and their transitive dependencies, ensuring consistent installations.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

Changelog
  • package.json
    • Updated @apollo/server from ^4.9.3 to ^5.4.0
    • Updated @nestjs/apollo from ^12.0.7 to ^13.0.0
    • Updated @nestjs/platform-express from 10.4.2 to 10.4.22
    • Updated @nestjs/swagger from 6.3.0 to 11.2.6
    • Updated express from ^4.18.2 to ^4.22.0
  • pnpm-lock.yaml
    • Updated @apollo/server to 5.4.0
    • Updated @nestjs/apollo to 13.2.4
    • Updated @nestjs/core to reference @nestjs/platform-express@10.4.22
    • Updated @nestjs/platform-express to 10.4.22
    • Updated @nestjs/serve-static to reference express@4.22.1
    • Updated @nestjs/swagger to 11.2.6
    • Updated @nestjs/testing to reference @nestjs/platform-express@10.4.22
    • Updated @graphql-tools/merge to 9.0.0 and removed older version 8.4.2
    • Updated @graphql-tools/schema to 10.0.0 and removed older version 9.0.19
    • Updated @graphql-tools/utils to 10.0.0 and removed older version 9.2.1
    • Removed @josephg/resolvable dependency
    • Added @microsoft/tsdoc dependency
    • Updated body-parser to 1.20.4 and 2.2.2
    • Updated cookie to 0.7.2
    • Updated cors to 2.8.6
    • Added debug@4.4.3 dependency
    • Updated encodeurl to 2.0.0
    • Added es-define-property, es-errors, es-object-atoms dependencies
    • Updated express to 4.22.1
    • Updated finalhandler to 1.3.2 and 2.1.1
    • Removed form-data@3.0.1 dependency
    • Added fresh@2.0.0 dependency
    • Updated function-bind to 1.1.2
    • Added get-intrinsic@1.3.0, get-proto@1.0.1, gopd@1.2.0 dependencies
    • Updated has-symbols to 1.1.0
    • Added hasown dependency
    • Updated http-errors to 2.0.1
    • Updated iconv-lite to 0.7.2
    • Updated js-yaml to 4.1.1
    • Updated lodash to 4.17.23
    • Updated lru-cache to 11.2.6 and removed older version 7.18.3
    • Added math-intrinsics dependency
    • Updated media-typer to 1.1.0
    • Updated mime-db to 1.54.0
    • Updated mime-types to 3.0.2
    • Removed minimatch@8.0.4 and minipass@4.2.8 dev dependencies
    • Updated multer to 1.4.5-lts.1 and 2.0.2
    • Updated negotiator to 1.0.0
    • Removed node-abort-controller dev dependency
    • Added object-inspect@1.13.4 dependency
    • Updated path-to-regexp to 0.1.12 and 8.3.0
    • Updated qs to 6.14.2 and 6.15.0
    • Updated raw-body to 2.5.3 and 3.0.2
    • Removed rimraf@3.0.2 dev dependency
    • Updated send to 0.19.2 and 1.2.1
    • Updated serve-static to 1.16.3
    • Added side-channel-list, side-channel-map, side-channel-weakmap dependencies
    • Updated side-channel to 1.1.0
    • Updated statuses to 2.0.2
    • Updated swagger-ui-dist to 5.31.0
    • Updated tslib to 2.8.1 and removed older version 2.6.0
    • Updated type-is to 2.0.1
    • Updated uuid to 11.1.0
    • Updated whatwg-mimetype to 4.0.0
Activity
  • This pull request was automatically created by Snyk to address identified vulnerabilities in the project's pnpm dependencies.
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.

Copy link

@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 fix security vulnerabilities by upgrading several dependencies. While this is important, the upgrades include major version bumps for @nestjs/apollo (v12 to v13) and @nestjs/swagger (v6 to v11). These new versions have peer dependency requirements for other @nestjs packages (like @nestjs/common and @nestjs/core) at version 11, but your project currently uses version 9 for these core packages. This version mismatch is highly likely to cause build failures or runtime errors. It is recommended to either perform a full upgrade of the entire NestJS framework to a consistent major version, or find alternative ways to patch the vulnerabilities without introducing these breaking changes. Additionally, the upgrade of @apollo/server to v5 now requires Node.js version 20 or higher, which is another potential breaking change to be aware of.

"@apollo/server": "^4.9.3",
"@nestjs/apollo": "^12.0.7",
"@apollo/server": "^5.4.0",
"@nestjs/apollo": "^13.0.0",

Choose a reason for hiding this comment

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

critical

The new version 13.x of @nestjs/apollo requires @nestjs/common and @nestjs/core version ^11.0.1. However, your project is still using version 9.4.2 for these packages. This major version mismatch will likely break your application. You should consider upgrading all @nestjs/* packages to a consistent major version (e.g., v10 or v11) to ensure compatibility.

"@nestjs/schedule": "^2.2.2",
"@nestjs/serve-static": "^3.0.1",
"@nestjs/swagger": "6.3.0",
"@nestjs/swagger": "11.2.6",

Choose a reason for hiding this comment

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

critical

Similar to the @nestjs/apollo upgrade, version 11.x of @nestjs/swagger has a peer dependency on @nestjs/common and @nestjs/core version ^11.0.1. Your project's use of version 9.4.2 for these core packages is incompatible. This is likely to cause build or runtime errors. A full framework upgrade is recommended for compatibility.

"dependencies": {
"@apollo/server": "^4.9.3",
"@nestjs/apollo": "^12.0.7",
"@apollo/server": "^5.4.0",

Choose a reason for hiding this comment

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

high

This is a major version upgrade. Please be aware that @apollo/server@5.x requires Node.js version 20 or higher. Your project should be tested against this new Node.js version requirement to ensure it doesn't break your deployment environment.

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