Skip to content

Comments

[Snyk] Security upgrade next from 15.3.5 to 15.3.8#18

Merged
Dargon789 merged 1 commit intomainfrom
snyk-fix-f6ea5e60874bd07c64dfc75a5475d70a
Dec 15, 2025
Merged

[Snyk] Security upgrade next from 15.3.5 to 15.3.8#18
Dargon789 merged 1 commit intomainfrom
snyk-fix-f6ea5e60874bd07c64dfc75a5475d70a

Conversation

@Dargon789
Copy link
Owner

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 Deserialization of Untrusted Data
SNYK-JS-NEXT-14400636
  852  
medium severity Exposure of Sensitive System Information to an Unauthorized Control Sphere
SNYK-JS-NEXT-14400644
  678  

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:

🦉 Deserialization of Untrusted Data

@vercel
Copy link
Contributor

vercel bot commented Dec 14, 2025

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Review Updated (UTC)
arcjet-example Ready Ready Preview, Comment Dec 14, 2025 3:55pm
arcjet-example-pvhg Ready Ready Preview, Comment Dec 14, 2025 3:55pm

@snyk-io
Copy link
Contributor

snyk-io bot commented Dec 14, 2025

Snyk checks have passed. No issues have been found so far.

Status Scanner Critical High Medium Low Total (0)
Open Source Security 0 0 0 0 0 issues

💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse.

@gemini-code-assist
Copy link

Summary of Changes

Hello @Dargon789, 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 aims to bolster the project's security by updating the next framework dependency. The update specifically targets and resolves critical vulnerabilities related to data deserialization and potential exposure of sensitive system information, thereby enhancing the overall security posture of the application.

Highlights

  • Security Upgrade: This pull request, automatically generated by Snyk, upgrades the next dependency from version 15.3.5 to 15.3.8.
  • Vulnerability Fixes: The upgrade addresses two identified vulnerabilities: a high-severity 'Deserialization of Untrusted Data' (SNYK-JS-NEXT-14400636) and a medium-severity 'Exposure of Sensitive System Information to an Unauthorized Control Sphere' (SNYK-JS-NEXT-14400644).
  • Dependency Updates: The changes primarily involve updating the version of next in package.json and package-lock.json, along with the corresponding @next/env dependency and integrity hashes in package-lock.json.
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, upgrades the next package from version 15.3.5 to 15.3.8 to resolve two security vulnerabilities. The update is necessary and correctly applied in package.json. However, there is a minor inconsistency in package-lock.json where the next dependency is specified with a caret (^15.3.8) instead of being pinned, which mismatches the intent in package.json. I've left a comment with a suggestion to fix this to ensure dependency resolution is consistent and predictable.

"@nosecone/next": "1.0.0-beta.9",
"@oddbird/css-anchor-positioning": "0.6.1",
"next": "15.3.5",
"next": "^15.3.8",

Choose a reason for hiding this comment

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

medium

There's an inconsistency between package.json and package-lock.json. package.json pins the next version to 15.3.8, but here in package-lock.json it's specified with a caret as ^15.3.8. While the resolved version is correct for now, this can lead to confusion and unexpected behavior in the future. To fix this, you should run npm install to regenerate the lock file based on the pinned version in package.json.

Suggested change
"next": "^15.3.8",
"next": "15.3.8",

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.

[vc]: #[Snyk] Security upgrade @playwright/test from 1.54.1 to 1.55.1 #7 [vc]: #deps: bump next from 15.3.5 to 15.5.9 (#17)

2 participants