[Snyk] Security upgrade next from 15.3.2 to 15.3.6#10
Conversation
The following vulnerabilities are fixed with an upgrade: - https://snyk.io/vuln/SNYK-JS-NEXT-14173355
Summary of ChangesHello @nn6n, 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 by updating the Highlights
Using Gemini Code AssistThe 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
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 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
|
There was a problem hiding this comment.
Code Review
This pull request, automatically generated by Snyk, upgrades the next package from version 15.3.2 to 15.3.6. This is a critical security update that resolves an "Arbitrary Code Injection" vulnerability (SNYK-JS-NEXT-14173355). However, the pnpm-lock.yaml file has not been updated to reflect this change, which means the vulnerability will not be fixed in deployments. I've added a critical comment with details on how to resolve this. Once the lock file is updated, this pull request will be ready to merge.
| "mem0ai": "^2.1.25", | ||
| "motion": "^12.10.5", | ||
| "next": "^15.3.2", | ||
| "next": "^15.3.6", |
There was a problem hiding this comment.
While the next dependency has been updated in package.json, the pnpm-lock.yaml file has not been updated to reflect this change. The lock file still points to next@15.3.2. To ensure the security vulnerability is actually fixed, the lock file must be updated by running pnpm install and the resulting pnpm-lock.yaml file must be committed to this pull request. Without this, the vulnerable version of next will still be installed.
Snyk has created this PR to fix 1 vulnerabilities in the npm dependencies of this project.
Snyk changed the following file(s):
package.jsonVulnerabilities that will be fixed with an upgrade:
SNYK-JS-NEXT-14173355
Important
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:
🦉 Arbitrary Code Injection