-
Notifications
You must be signed in to change notification settings - Fork 679
[Repo] Restore dependencies to known-good lockfile #8892
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Closed
Closed
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
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
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
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
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
Large diffs are not rendered by default.
Oops, something went wrong.
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
🔒 Security & Privacy | 🟠 Major | ⚡ Quick win
🧩 Analysis chain
🏁 Script executed:
Repository: thirdweb-dev/js
Length of output: 32401
🌐 Web query:
Next.js GHSA-h25m-26qc-wcjf CVE-2026-23864 patched versions 15.3.9💡 Result:
Next.js version 15.3.9 is a patched version that addresses the vulnerability tracked as GHSA-h25m-26qc-wcjf and CVE-2026-23864 [1][2]. This vulnerability is a Denial of Service (DoS) issue affecting React Server Components [1][3]. It allows a specially crafted HTTP request sent to an App Router Server Function endpoint to trigger excessive CPU usage, out-of-memory exceptions, or server crashes [1][2]. The issue stems from insecure deserialization within React Server Components packages (such as react-server-dom-webpack), which are utilized by various frameworks including Next.js versions 13.x, 14.x, 15.x, and 16.x [2][3]. For Next.js, the following versions were released to patch this vulnerability: 15.0.8, 15.1.12, 15.2.9, 15.3.9, 15.4.11, 15.5.10, 15.6.0-canary.61, 16.0.11, and 16.1.5 [1][2]. Users running affected versions are strongly encouraged to upgrade to one of these patched releases to mitigate the risk of availability issues [2][3].
Citations:
🌐 Web query:
site:nextjs.org/blog July 20 2026 Next.js security release patched 15.5.x 16.2.x💡 Result:
On July 20, 2026, Next.js released security patches as part of its newly formalized monthly security release program [1][2]. This update addressed 4 high-severity and 5 medium-severity vulnerabilities [1][2]. The security patches were made available in the following versions [1]: - Next.js 16.2.11 (Active LTS) - Next.js 15.5.21 (Maintenance LTS) Users are advised to upgrade their dependencies to these versions to secure their applications [1]. These fixes are also included in the latest Next.js 16.3 canary (v16.3.0-canary.92) and preview (v16.3.0-preview.7) releases [1]. Although the security release program initially anticipated a publication date of July 21, 2026, the updates were published on July 20, 2026 [3][4][2].
Citations:
🏁 Script executed:
Repository: thirdweb-dev/js
Length of output: 50371
🌐 Web query:
Next.js 15.5.21 release Node.js requirements compatibility React 19.2💡 Result:
Next.js 15.5.21 is a security-focused release [1][2]. Below are the compatibility and requirement details as of August 13, 2026: Node.js Requirements The minimum supported version of Node.js for Next.js 15 is Node.js 20.9.0 [3][4]. This requirement was established as a breaking change to ensure compatibility with modern LTS releases [4]. React 19 Compatibility Next.js 15 is built to align with React 19 [5]. - App Router: Internally utilizes React 19 (often via the Canary channel) [5][6]. - Pages Router: Next.js 15.1 and subsequent versions include official support for stable React 19 [7][8]. While Next.js 15 provides some backward compatibility for React 18, it is not recommended to mix React 18 and 19 within the same application due to potential inconsistencies in rendering logic and API behavior [5]. Security Context Version 15.5.21 was released on July 21, 2026, to address multiple security vulnerabilities, including issues related to Server-Side Request Forgery (SSRF), middleware authorization bypass, and denial of service (DoS) [1][2]. It is strongly recommended to upgrade to this version (or 16.2.11) if you are currently on an older 15.x minor release [2]. Note that Next.js 15 is currently in Maintenance LTS and is scheduled to reach End-of-Life (EOL) on October 21, 2026 [9][10][11].
Citations:
>=20.9.0vercel/next.js#83113🌐 Web query:
site:nextjs.org/blog/july-2026-security-release Next.js 15.5.21 vulnerabilities supported versions💡 Result:
Next.js 15.5.21 is a supported version categorized as Maintenance LTS [1]. This version was released in July 2026 to address security vulnerabilities [1]. To update your application to this version, use the following command: npm install next@15.5.21 [1] For users on the Active LTS branch, updates are available in version 16.2.11 [1]. It is recommended to patch dependencies to the latest available versions to ensure application security [1].
Citations:
🏁 Script executed:
Repository: thirdweb-dev/js
Length of output: 1593
🌐 Web query:
Next.js 15.5.21@next/mdx15.5.21@next/eslint-plugin-next15.5.21@next/bundle-analyzer15.5.21 peer dependencies💡 Result:
Next.js 15.5.21 was a security-focused release published on July 21, 2026, to address multiple vulnerabilities, including issues related to Server Actions, Middleware, and SSRF [1][2][3]. Regarding your specific query on peer dependencies for version 15.5.21 and associated packages: 1. Peer Dependency Structure: In the Next.js ecosystem, packages like
@next/mdx,@next/eslint-plugin-next, and@next/bundle-analyzerare maintained within the same monorepo as the core next package [1][4]. They typically define a peer dependency on the next package itself [5]. 2. Version Matching: For the 15.x maintenance branch, it is standard practice to match the version of these utility packages to the version of the core next package (i.e., 15.5.21) to ensure compatibility and avoid potential runtime issues [5][4]. 3. Current Context: As of August 13, 2026, Next.js 15.5.21 is a Maintenance LTS release [2][6]. Note that more recent versions exist, such as 15.5.23 (released August 6, 2026) [6] and the major version Next.js 16.3.0 (released August 3, 2026) [7][8]. If you are managing a project currently on 15.5.21, ensuring all related@next/* packages are also updated to 15.5.21 is the recommended approach to align with the core framework's security patches and internal dependency requirements [5][4]. Always verify your package.json ensures that peer dependency constraints are satisfied, typically by keeping all@nextscoped packages at the same minor/patch version as your installed next core package [5].Citations:
Update the Next.js dependency set before merge.
All six manifests and
pnpm-lock.yamlresolvenext@15.3.8, which remains affected. Upgrade to a currently patched supported 15.5.x release. Align the related@next/*packages andeslint-config-nextwhere present, then regenerate the lockfile.📍 Affects 6 files
apps/dashboard/package.json#L47-L47(this comment)apps/nebula/package.json#L23-L23apps/playground-web/package.json#L31-L31apps/portal/package.json#L24-L24apps/wallet-ui/package.json#L13-L13packages/ui/package.json#L28-L28🤖 Prompt for AI Agents
Source: MCP tools