[Snyk] Security upgrade next from 15.3.1 to 15.3.6

[KB01111]

User description

Snyk has created this PR to fix 2 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	Score
	Arbitrary Code Injection SNYK-JS-NEXT-14173355	893
	Improper Verification of Cryptographic Signature SNYK-JS-PLAYWRIGHTCORE-13553173	514

---

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:

🦉 Arbitrary Code Injection

---

CodeAnt-AI Description

Upgrade Next.js in frontend to fix critical security vulnerabilities

What Changed

• Upgraded the frontend dependency on Next.js from 15.3.1 to 15.3.6 to address reported vulnerabilities.
• Fixes an arbitrary code injection vulnerability and an improper cryptographic signature verification issue in related packages.
• No deliberate UI or API behavior changes; this is a dependency security patch.

Impact

✅ Fewer dependency vulnerabilities
✅ Lower risk of arbitrary code execution in the frontend dependency chain
✅ Lower risk of accepting tampered browser/test artifacts

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.

[codemetrics-ai]

⚠️ Your Codemetrics free trial has expired. To continue using AI based pull request reviews, please subscribe to premium in team settings.

[coderabbitai]

Important

Review skipped

Ignore keyword(s) in the title.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

✨ Finishing touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch snyk-fix-9eab085d0fbc319d60abc204764e15d2

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[codeant-ai]

CodeAnt AI is reviewing your PR.

---

Thanks for using CodeAnt! 🎉

We're free for open-source projects. if you're enjoying it, help us grow by sharing.

Share on X ·
Reddit ·
LinkedIn

[gemini-code-assist]

Summary of Changes

Hello @KB01111, 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, automatically generated by Snyk, updates the 'next' dependency in the 'frontend/package.json' file. The primary purpose of this upgrade is to mitigate critical and medium-severity security vulnerabilities, thereby enhancing the overall security posture of the project's frontend by addressing known exploits.

Highlights

• Security Upgrade: Upgrades the 'next' dependency from version '15.3.1' to '15.3.6' to address identified security vulnerabilities.
• Vulnerability Fixes: Resolves a critical 'Arbitrary Code Injection' vulnerability (SNYK-JS-NEXT-14173355) and a medium severity 'Improper Verification of Cryptographic Signature' vulnerability (SNYK-JS-PLAYWRIGHTCORE-13553173).

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

[codeant-ai]

CodeAnt AI finished reviewing your PR.

[Copilot]

Pull request overview

This is an automated security upgrade PR from Snyk that updates Next.js from version 15.3.1 to 15.3.6 to address two security vulnerabilities: a critical Arbitrary Code Injection vulnerability (score: 893) and a medium severity Improper Verification of Cryptographic Signature vulnerability (score: 514).

• Updates Next.js dependency from 15.3.1 to 15.3.6 in package.json
• Addresses critical security vulnerability SNYK-JS-NEXT-14173355
• Addresses medium security vulnerability SNYK-JS-PLAYWRIGHTCORE-13553173

---

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

[gemini-code-assist]

Code Review

This pull request correctly upgrades the next package to version 15.3.6 to address security vulnerabilities. However, the PR is incomplete as the pnpm-lock.yaml file has not been updated, which will likely cause your build to fail. Additionally, the related eslint-config-next package should also be updated to match the new next version for consistency. I've left a detailed comment on the change in package.json.

[gemini-code-assist]

While updating next to 15.3.6 is correct, this PR is incomplete and will likely fail your CI build.

1. Inconsistent Lock File: The pnpm-lock.yaml has not been updated to reflect this change. It still specifies next@15.3.1, which will conflict with package.json. Please run pnpm install to update the lock file and commit the changes. Your Dockerfile uses pnpm install --frozen-lockfile, which will fail with this inconsistency.
2. Outdated ESLint Config: The eslint-config-next package in devDependencies is still at version 15.3.1. It is a strong best practice to keep this aligned with your next version to prevent linting rule mismatches. Please consider updating it to 15.3.6.

You can fix both issues by manually editing eslint-config-next in package.json and then running pnpm install.