[Snyk] Security upgrade next from 14.2.15 to 15.5.10

[iamdrewfortini]

Snyk has created this PR to fix 1 vulnerabilities in the pnpm dependencies of this project.

Snyk changed the following file(s):

• examples/cjs-test/package.json

⚠️ Warning

Failed to update the pnpm-lock.yaml, please update manually before merging.

Vulnerabilities that will be fixed with an upgrade:

	Issue	Score
	Allocation of Resources Without Limits or Throttling SNYK-JS-NEXT-15104645	149

---

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

[gemini-code-assist]

Summary of Changes

Hello @iamdrewfortini, I'm Gemini Code Assist¹! 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 automates a critical security update for the project's 'next' dependency, aiming to mitigate a high-severity vulnerability. The change involves a direct version bump in the 'package.json' file, ensuring the application benefits from the latest security patches and improved resource handling.

Highlights

• Security Upgrade: This pull request, automatically generated by Snyk, addresses a high-severity vulnerability (SNYK-JS-NEXT-15104645) related to 'Allocation of Resources Without Limits or Throttling' by upgrading the 'next' dependency.
• Dependency Version Update: The 'next' dependency in 'examples/cjs-test/package.json' has been updated from version '^14.1' to '^15.5.10'.
• Manual Intervention Required: A warning indicates that the 'pnpm-lock.yaml' file failed to update automatically and requires manual resolution before the pull request can be merged.

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. ↩

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	next@​15.2.3
	eslint-config-next@​15.2.3
	@​types/​react-dom@​19.1.9
	npm-run-all@​4.1.5
	@​stackframe/​stack-shared@​2.8.39
	@​types/​react@​19.1.13
	@​tailwindcss/​postcss@​4.1.13
	@​types/​node@​20.19.17
	rimraf@​5.0.10
	postcss@​8.5.6
	tailwindcss@​4.1.13
	wait-on@​8.0.5
	react@​19.1.1
	@​eslint/​eslintrc@​3.3.0 ⏵ 3.3.1
	convex@​1.27.0
	typescript@​5.9.2
	react-dom@​19.1.1
	prettier@​3.6.2
	eslint@​9.36.0
	@​stackframe/​stack@​2.8.39
	convex@​1.27.2

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Critical CVE: Next.js is vulnerable to RCE in React flight protocol CVE: GHSA-9qr9-h5gf-34mp Next.js is vulnerable to RCE in React flight protocol (CRITICAL) Affected versions: >= 14.3.0-canary.77 < 15.0.5; >= 15.1.0-canary.0 < 15.1.9; >= 15.2.0-canary.0 < 15.2.6; >= 15.3.0-canary.0 < 15.3.6; >= 15.4.0-canary.0 < 15.4.8; >= 15.5.0-canary.0 < 15.5.7; >= 16.0.0-canary.0 < 16.0.7 Patched version: 15.2.6 From: examples/convex/package-lock.json → npm/next@15.2.3 ℹ Read more on: This package | This alert | What is a critical CVE? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Remove or replace dependencies that include known critical CVEs. Consumers can use dependency overrides or npm audit fix --force to remove vulnerable dependencies. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/next@15.2.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: npm vite is 91.0% likely obfuscated Confidence: 0.91 Location: Package overview From: pnpm-lock.yaml → npm/vite@6.1.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore npm/vite@6.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[gemini-code-assist]

Code Review

This pull request, automatically generated by Snyk, upgrades the next package from version 14 to 15 in the examples/cjs-test project to fix a security vulnerability. While the upgrade is necessary, the pull request is incomplete as it fails to update the pnpm-lock.yaml file. This is a critical issue that will cause dependency inconsistencies and must be fixed before merging. Additionally, this is a major version upgrade with breaking changes, which requires careful consideration.

[gemini-code-assist]

This dependency upgrade introduces two significant risks:

1. Incomplete Change: According to the pull request description, pnpm-lock.yaml failed to update. Merging this change without the corresponding lockfile update will lead to inconsistent dependencies and likely break the build. The lockfile must be generated and included in this pull request.

2. Breaking Change: This is a major version upgrade from Next.js v14 to v15. As noted in the PR description (isBreakingChange:true), this introduces breaking changes that may affect the application's functionality.