Skip to content

[Snyk] Security upgrade next from 16.2.10 to 16.2.11#5

Open
CrashBytes wants to merge 1 commit into
mainfrom
snyk-fix-bba5bcfd031930734f6929a11e29de0e
Open

[Snyk] Security upgrade next from 16.2.10 to 16.2.11#5
CrashBytes wants to merge 1 commit into
mainfrom
snyk-fix-bba5bcfd031930734f6929a11e29de0e

Conversation

@CrashBytes

Copy link
Copy Markdown
Owner

snyk-top-banner

Snyk has created this PR to fix 2 vulnerabilities in the yarn dependencies of this project.

Snyk changed the following file(s):

  • client/package.json
  • client/yarn.lock

Note for zero-installs users

If you are using the Yarn feature zero-installs that was introduced in Yarn V2, note that this PR does not update the .yarn/cache/ directory meaning this code cannot be pulled and immediately developed on as one would expect for a zero-install project - you will need to run yarn to update the contents of the ./yarn/cache directory.
If you are not using zero-install you can ignore this as your flow should likely be unchanged.

Vulnerabilities that will be fixed with an upgrade:

Issue
high severity Server-side Request Forgery (SSRF)
SNYK-JS-NEXT-18233136
high severity Server-side Request Forgery (SSRF)
SNYK-JS-NEXT-18233752

Breaking Change Risk

Merge Risk: Low

Notice: This assessment is enhanced by AI.


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:

🦉 Server-side Request Forgery (SSRF)

@CrashBytes

Copy link
Copy Markdown
Owner Author

Merge Risk: Low

This is a patch version upgrade from next@16.2.10 to next@16.2.11. According to official announcements, this release is part of a security update to address multiple vulnerabilities.

As a patch release focused on security, it is not expected to contain breaking API changes. The changelog for the preceding version, v16.2.10, also indicates it contained no functional changes.

Recommendation: Given this is a security release, upgrading is recommended. No breaking changes are anticipated.

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

Copilot AI review requested due to automatic review settings July 23, 2026 13:41
@sonarqubecloud

Copy link
Copy Markdown

Copilot AI left a comment

Copy link
Copy Markdown

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 updates the client application’s Next.js dependency from 16.2.10 to 16.2.11 to address Snyk-reported SSRF vulnerabilities, and refreshes the Yarn lockfile accordingly.

Changes:

  • Bump next in client/package.json to ^16.2.11.
  • Update client/yarn.lock to reflect the Next.js upgrade and resulting dependency graph changes.

Reviewed changes

Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.

File Description
client/package.json Updates the Next.js dependency version to the patched release.
client/yarn.lock Refreshes locked dependency versions/transitives to match the upgraded Next.js release.

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

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