Hotfix/web 380 CVE next#381
Merged
Merged
Conversation
There was a problem hiding this comment.
Pull request overview
This PR addresses critical security vulnerabilities (CVE-380) by upgrading Next.js from version 15.1.8 to 15.5.7, along with updating related dependencies to resolve additional CVEs identified by npm audit. The update represents a minor version jump for Next.js and includes patches for React, SWR, ESLint tooling, and various optional dependencies like Sharp image processing libraries.
Key Changes
- Next.js upgrade: From ~15.1.8 to ^15.5.7 (minor version upgrade with versioning strategy change from tilde to caret)
- React ecosystem updates: React and React-DOM updated from ^19.0.0 to ^19.0.1 (patch update)
- Development tooling: ESLint config, Prettier plugin, and related tooling updated to latest compatible versions
- Transitive dependency updates: Numerous security patches for indirect dependencies including Sharp, ESLint core components, and various build tools
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| application/package.json | Updates 8 direct dependencies: Next.js, @next/third-parties, React, React-DOM, SWR (runtime) and eslint-config-next, prettier-plugin-tailwindcss (dev). Changes Next.js version constraint from tilde (~) to caret (^). |
| application/package-lock.json | Comprehensive lockfile update with hundreds of transitive dependency version updates, including security patches for @eslint/* packages, @img/sharp-* platform-specific binaries, and removal of deprecated dependencies like @swc/counter, busboy, color, and streamsearch. |
Files not reviewed (1)
- application/package-lock.json: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
jbuiquan
force-pushed
the
hotfix/web-380-cve-next
branch
from
December 6, 2025 18:04
366e078 to
60da89f
Compare
Oce-ane
approved these changes
Dec 8, 2025
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Github issue : #380
Cette PR a pour objectif de corriger la vulnérabilité critique associé à l'issue.
En complément, la version mineure de Next a été upgradé pour corriger d'autre CVE critiques remontées par l'audit
npm(voir issue).Des patchs d'autres dépendances sont aussi intégrées.
Comment tester ?
npm run buildet navigation sur l'appli OKPour faciliter la validation de ma PR