Skip to content

[Snyk] Security upgrade eslint-config-next from 14.1.0 to 15.0.0#31

Open
anonthedev wants to merge 1 commit into
mainfrom
snyk-fix-ff0ae83d2bc8a22ecffee5618bd78976
Open

[Snyk] Security upgrade eslint-config-next from 14.1.0 to 15.0.0#31
anonthedev wants to merge 1 commit into
mainfrom
snyk-fix-ff0ae83d2bc8a22ecffee5618bd78976

Conversation

@anonthedev

@anonthedev anonthedev commented Feb 4, 2026

Copy link
Copy Markdown
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 Regular Expression Denial of Service (ReDoS)
SNYK-JS-CROSSSPAWN-8303230
  756  
low severity Regular Expression Denial of Service (ReDoS)
SNYK-JS-BRACEEXPANSION-9789073
  436  

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:

🦉 Regular Expression Denial of Service (ReDoS)


Note

Medium Risk
Dependency-only change, but it upgrades the Next.js ESLint config and multiple linting transitive packages, which may introduce new lint rules/behavior or Node/ESLint peer/engine constraints in CI.

Overview
Updates linting dependencies by upgrading eslint-config-next from 14.1.0 to 15.0.0 in package.json, with the corresponding package-lock.json refresh.

The lockfile reflects the new Next ESLint stack (updated @next/eslint-plugin-next, @rushstack/eslint-patch, @typescript-eslint/*, and related ESLint plugins/utilities), addressing reported ReDoS vulnerabilities in transitive packages.

Written by Cursor Bugbot for commit bf5c55a. This will update automatically on new commits. Configure here.

@vercel

vercel Bot commented Feb 4, 2026

Copy link
Copy Markdown

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

Project Deployment Actions Updated (UTC)
youify Ready Ready Preview, Comment Feb 4, 2026 0:07am

@cursor cursor Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Cursor Bugbot has reviewed your changes and found 1 potential issue.

Bugbot Autofix is OFF. To automatically fix reported issues with Cloud Agents, enable Autofix in the Cursor dashboard.

This PR is being reviewed by Cursor Bugbot

Details

You are on the Bugbot Free tier. On this plan, Bugbot will review limited PRs each billing cycle.

To receive Bugbot reviews on all of your PRs, visit the Cursor dashboard to activate Pro and start your 14-day free trial.

Comment thread package.json
"axios": "^1.3.6",
"eslint": "8.36.0",
"eslint-config-next": "14.1.0",
"eslint-config-next": "15.0.0",

Copy link
Copy Markdown

Choose a reason for hiding this comment

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

Major version mismatch between eslint-config-next and Next.js

Medium Severity

The eslint-config-next package is being upgraded from 14.1.0 to 15.0.0, but the project uses next: "13.2.4". The eslint-config-next version is typically kept in sync with the Next.js version. Using version 15.0.0 with Next.js 13 creates a significant version mismatch that may cause ESLint rules designed for Next.js 15 features to incorrectly flag or miss issues in a Next.js 13 codebase. Additionally, the transitive dependencies now require Node.js 18.18.0+ which may be stricter than before.

Additional Locations (1)

Fix in Cursor Fix in Web

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.

2 participants