update npm packages to fix a react/next CVE #86
Conversation
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
Contributor
There was a problem hiding this comment.
Pull request overview
This PR updates npm dependencies to address a React Server Components security vulnerability. The primary changes are updating React from 19.2.3 to 19.2.4, React-DOM from 19.2.3 to 19.2.4, and Next.js from 16.0.10 to 16.1.6 to fix CVE-2025-23864 (noted as CVE-2026-23864 in the PR description, which appears to be a typo).
Changes:
- Updated React and React-DOM to 19.2.4 to address security vulnerability
- Updated Next.js to 16.1.6 to address security vulnerability
- Updated various transitive dependencies including Babel, TypeScript ESLint, and other development tooling packages
Reviewed changes
Copilot reviewed 1 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| web/package.json | Updated main dependencies: Next.js (^16.0.10 → ^16.1.6), React (^19.2.3 → ^19.2.4), and React-DOM (^19.2.3 → ^19.2.4) |
| web/pnpm-lock.yaml | Lockfile updates for all direct and transitive dependencies affected by the main package updates |
Files not reviewed (1)
- web/pnpm-lock.yaml: Language not supported
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
this updates all our npm deps to the latest versions but is mostly so we can update react and next.js to fix this new CVE (different from the one in december) https://vercel.com/changelog/summary-of-cve-2026-23864 > Summary > Multiple high-severity vulnerabilities in React Server Components were responsibly disclosed. Importantly, these vulnerabilities do not allow for Remote Code Execution.
ryankshaw
force-pushed
the
ry/react-cve-jan-2026
branch
from
7f4878c to
7b04c2f
Compare
JoshMDiaz
approved these changes
Jan 29, 2026
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.
this updates all our npm deps to the latest versions but is mostly so we can update react and next.js to fix this new CVE (different from the one in december)
https://vercel.com/changelog/summary-of-cve-2026-23864