Skip to content

[Snyk] Security upgrade next from 15.5.10 to 16.1.5#37

Open
SMSDAO wants to merge 1 commit intomainfrom
snyk-fix-5b1380197374e0aca1390f6231f0d2ab
Open

[Snyk] Security upgrade next from 15.5.10 to 16.1.5#37
SMSDAO wants to merge 1 commit intomainfrom
snyk-fix-5b1380197374e0aca1390f6231f0d2ab

Conversation

@SMSDAO
Copy link
Contributor

@SMSDAO SMSDAO commented Jan 28, 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):

  • frontend/package.json

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Allocation of Resources Without Limits or Throttling
SNYK-JS-NEXT-15105315

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

Copilot AI review requested due to automatic review settings January 28, 2026 21:34
@github-actions
Copy link

📢 New Pull Request Ready for Review

Title: [Snyk] Security upgrade next from 15.5.10 to 16.1.5
Author: @SMSDAO
Branch: snyk-fix-5b1380197374e0aca1390f6231f0d2abmain

Please review when you have a chance! 🚀

Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

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

Pull request overview

This PR upgrades Next.js from version 15.1.2 to 16.1.5 to address a high-severity security vulnerability (SNYK-JS-NEXT-15105315) related to "Allocation of Resources Without Limits or Throttling".

Changes:

  • Upgrade Next.js dependency from ^15.1.2 to ^16.1.5 in frontend/package.json

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

},
"dependencies": {
"next": "^15.1.2",
"next": "^16.1.5",
Copy link

Copilot AI Jan 28, 2026

Choose a reason for hiding this comment

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

The PR description mentions upgrading from Next.js 15.5.10, but the actual change shows an upgrade from ^15.1.2 to ^16.1.5. This is a discrepancy between the PR title and the actual code change. The change itself appears correct as ^16.1.5 will fix the security vulnerability, but the PR metadata may be inaccurate.

Copilot uses AI. Check for mistakes.
Comment on lines 16 to 17
"react": "^18.3.1",
"react-dom": "^18.3.1",
Copy link

Copilot AI Jan 28, 2026

Choose a reason for hiding this comment

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

Next.js 16 requires React 19 or later. The current React version (^18.3.1) is incompatible with Next.js 16. Both 'react' and 'react-dom' need to be upgraded to ^19.0.0 or later. The package-lock.json already shows React 19, indicating there's a mismatch between package.json and package-lock.json.

Copilot uses AI. Check for mistakes.
"next": "^16.1.5",
"react": "^18.3.1",
"react-dom": "^18.3.1",
"next-auth": "^4.24.5",
Copy link

Copilot AI Jan 28, 2026

Choose a reason for hiding this comment

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

NextAuth.js v4 may not be fully compatible with Next.js 16. Next.js 16 is better supported by Auth.js v5 (the successor to NextAuth.js v4). Consider upgrading to '@auth/nextjs' (Auth.js v5) or verifying that next-auth v4.24.5 is compatible with Next.js 16 and React 19.

Copilot uses AI. Check for mistakes.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants