Skip to content

[Snyk] Security upgrade next from 15.3.1 to 15.3.8#16

Open
KB01111 wants to merge 1 commit intomainfrom
snyk-fix-0e48dfcd6aef1859cfee8a46e680ce59
Open

[Snyk] Security upgrade next from 15.3.1 to 15.3.8#16
KB01111 wants to merge 1 commit intomainfrom
snyk-fix-0e48dfcd6aef1859cfee8a46e680ce59

Conversation

@KB01111
Copy link
Copy Markdown
Owner

@KB01111 KB01111 commented Jan 12, 2026

User description

snyk-top-banner

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

Snyk changed the following file(s):

  • frontend/package.json
  • frontend/pnpm-lock.yaml

Vulnerabilities that will be fixed with an upgrade:

Issue Score
high severity Exposed Dangerous Method or Function
SNYK-JS-PLAYWRIGHT-14888269
  753  

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:

🦉 Learn about vulnerability in an interactive lesson of Snyk Learn.


CodeAnt-AI Description

Upgrade Next.js to 15.3.8 to fix a high-severity Playwright security issue

What Changed

  • Updated frontend dependency next from 15.3.1 to 15.3.8 and updated frontend lockfile entries accordingly
  • Updated related Next optional SWC binaries and package snapshots to newer patch versions
  • Resolves a Playwright vulnerability (Exposed Dangerous Method) reported by Snyk; no user-facing feature changes

Impact

✅ Fix Playwright high-severity vulnerability
✅ Lower frontend security risk
✅ No change to user-facing UI or behavior

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

Copilot AI review requested due to automatic review settings January 12, 2026 07:00
@codeant-ai
Copy link
Copy Markdown

codeant-ai bot commented Jan 12, 2026

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

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Jan 12, 2026

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-0e48dfcd6aef1859cfee8a46e680ce59

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

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

@gemini-code-assist
Copy link
Copy Markdown

Summary of Changes

Hello @KB01111, 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 automates a critical security update for the project's frontend dependencies. By upgrading the next framework to its latest patch version, it proactively mitigates a high-severity vulnerability, enhancing the overall security posture of the application. The update ensures that the project benefits from the latest security fixes without manual intervention.

Highlights

  • Security Upgrade: The next dependency has been upgraded from version 15.3.1 to 15.3.8 to address a high-severity security vulnerability.
  • Vulnerability Fixed: This PR specifically resolves the SNYK-JS-PLAYWRIGHT-14888269 vulnerability, categorized as "Exposed Dangerous Method or Function" with a score of 753.
  • Automated by Snyk: The changes were automatically generated by Snyk to ensure timely security patching.

🧠 New Feature in Public Preview: You can now enable Memory to help Gemini Code Assist learn from your team's feedback. This makes future code reviews more consistent and personalized to your project's style. Click here to enable Memory in your admin console.

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.

@codemetrics-ai
Copy link
Copy Markdown

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

@codeant-ai codeant-ai bot added the size:M This PR changes 30-99 lines, ignoring generated files label Jan 12, 2026
@codeant-ai
Copy link
Copy Markdown

codeant-ai bot commented Jan 12, 2026

Sequence Diagram

This PR updates frontend package.json and pnpm lock to move Next.js from 15.3.1 → 15.3.8, causing dependency installation and rebuild so the application uses the patched Next (and transitive Playwright) that resolves the reported vulnerability.

sequenceDiagram
    participant Snyk
    participant Repo
    participant PackageManager
    participant BuildSystem
    participant Runtime

    Snyk->>Repo: Open PR with upgraded frontend/package.json & pnpm-lock.yaml
    Repo->>PackageManager: Install dependencies (next@15.3.8)
    PackageManager-->>BuildSystem: Provide updated dependency graph
    BuildSystem->>Runtime: Build / deploy using next@15.3.8
    Runtime-->>Repo: Runs with patched transitive deps (Playwright) — vulnerability resolved
Loading

Generated by CodeAnt AI

@codeant-ai
Copy link
Copy Markdown

codeant-ai bot commented Jan 12, 2026

CodeAnt AI finished reviewing your PR.

@codeant-ai
Copy link
Copy Markdown

codeant-ai bot commented Jan 12, 2026

💡 Enhance Your PR Reviews

We noticed that 3 feature(s) are not configured for this repository. Enabling these features can help improve your code quality and workflow:

🚦 Quality Gates

Status: Quality Gates are not enabled at the organization level
Learn more about Quality Gates

🎫 Jira Ticket Compliance

Status: Jira credentials file not found. Please configure Jira integration in your settings
Learn more about Jira Integration

⚙️ Custom Rules

Status: No custom rules configured. Add rules via organization settings or .codeant/review.json in your repository
Learn more about Custom Rules


Want to enable these features? Contact your organization admin or check our documentation for setup instructions.

Copy link
Copy Markdown

Copilot AI left a comment

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 upgrades Next.js from version 15.3.1 to 15.3.8 to address a high-severity security vulnerability (SNYK-JS-PLAYWRIGHT-14888269) related to an exposed dangerous method or function in the Playwright dependency.

Changes:

  • Updated Next.js from 15.3.1 to 15.3.8 (patch version upgrade)
  • Updated all associated @next/* packages (env and SWC compiler binaries)
  • Updated transitive dependencies including caniuse-lite

Reviewed changes

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

File Description
frontend/package.json Updated Next.js version specifier from 15.3.1 to 15.3.8
frontend/pnpm-lock.yaml Updated Next.js and all related package resolutions, including @next/env, @next/swc-* binaries (to 15.3.5), and transitive dependencies like caniuse-lite
Files not reviewed (1)
  • frontend/pnpm-lock.yaml: Language not supported

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

Copy link
Copy Markdown

@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, correctly upgrades the next package from version 15.3.1 to 15.3.8 to resolve a security vulnerability. The changes in package.json and the corresponding updates in pnpm-lock.yaml are appropriate for this upgrade. I have added one recommendation to also update the related ESLint configuration package to ensure consistency.

"leaflet-defaulticon-compatibility": "^0.1.2",
"lucide-react": "^0.474.0",
"next": "15.3.1",
"next": "15.3.8",
Copy link
Copy Markdown

Choose a reason for hiding this comment

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

medium

While updating the next package is correct, it's a best practice to also update its corresponding ESLint configuration to maintain consistency and avoid potential linting issues. Please consider updating eslint-config-next in your devDependencies from 15.3.1 to 15.3.8 to match the new next version.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

size:M This PR changes 30-99 lines, ignoring generated files

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants