Skip to content

[Snyk] Fix for 2 vulnerabilities - #554

Closed
riddhi-desai wants to merge 1 commit into
developfrom
snyk-fix-c20432a94b22d098170b7349d9878fd7
Closed

[Snyk] Fix for 2 vulnerabilities#554
riddhi-desai wants to merge 1 commit into
developfrom
snyk-fix-c20432a94b22d098170b7349d9878fd7

Conversation

@riddhi-desai

Copy link
Copy Markdown
Contributor

snyk-top-banner

Snyk has created this PR to fix 2 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
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-QS-14724253
  127  
medium severity Prototype Pollution
SNYK-JS-JSYAML-13961110
  37  

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:

🦉 Prototype Pollution
🦉 Allocation of Resources Without Limits or Throttling

@riddhi-desai
riddhi-desai requested a review from a team as a code owner January 16, 2026 16:04
@riddhi-desai

Copy link
Copy Markdown
Contributor Author

Merge Risk: High

This upgrade includes a major version jump for @nestjs/swagger from v7 to v11, introducing significant breaking changes. The update for @nestjs/platform-express is a minor patch with low risk.

@nestjs/swagger 7.4.2 → 11.2.2 (High Risk):
This upgrade spans multiple major NestJS versions and requires attention to environment and code changes.

Highlights:

  • Node.js and TypeScript versions: NestJS v10 and later require Node.js v16+ and TypeScript v4.8+.
  • Express v5 Integration: NestJS v11 uses Express v5, which alters route path matching. Wildcard routes like /* must be changed to named parameters, e.g., /*splat.

Source: NestJS documentation, NestJS v10 & v11 release announcements.
Recommendation: Verify your Node.js and TypeScript versions are compatible. Review and update any route paths that use wildcards. Also, check tests related to dynamic modules, as their instantiation logic has changed in v11.

@nestjs/platform-express 10.4.20 → 10.4.22 (Low Risk):
This is a patch release that includes dependency updates for security fixes and should not introduce breaking changes.

Notice 🤖: This content was augmented using artificial intelligence. AI-generated content may contain errors and should be reviewed for accuracy before use.

@sb-benohe sb-benohe closed this Apr 23, 2026
@sb-benohe

Copy link
Copy Markdown
Contributor

✅ This PR has been automatically closed

The security issues addressed by this pull request are no longer present in the latest project scan. All vulnerabilities this PR was created to fix have been resolved through other means (e.g., dependency updates, direct fixes, or changes in vulnerability data).

Resolved Issues

  • SNYK-JS-JSYAML-13961110
  • SNYK-JS-QS-14724253

What should I do?

No action is required. If you believe this PR was closed in error, you can reopen it and contact Snyk support.


This action was performed automatically by Snyk.

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.

3 participants