Skip to content

build(deps): bump next from 16.2.2 to 16.2.3 in the npm_security group across 1 directory #29

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.

Sign up for GitHub

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

Merged
GeiserX merged 1 commit into from
Apr 10, 2026
Merged

build(deps): bump next from 16.2.2 to 16.2.3 in the npm_security group across 1 directory #29

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
80 changes: 40 additions & 40 deletions package-lock.json
View file
Open in desktop

Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.

2 changes: 1 addition & 1 deletion package.json
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -25,7 +25,7 @@
"dotenv": "^17.4.1",
"json5": "^2.2.3",
"maplibre-gl": "^5.22.0",
"next": "^16.2.2",
"next": "^16.2.3",
Copy link
Copy Markdown

@coderabbitai coderabbitai bot Apr 10, 2026

Choose a reason for hiding this comment

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

⚠️ Potential issue | 🟡 Minor

🧩 Analysis chain

🌐 Web query:

What is CVE-2026-23869 and which Next.js versions does it affect?

💡 Result:

CVE-2026-23869 is a high-severity (CVSS 7.5) denial-of-service vulnerability in React Server Components. A specially crafted HTTP request sent to App Router Server Function endpoints can trigger excessive CPU usage during deserialization, leading to DoS in unpatched environments. It originates in React packages: react-server-dom-parcel, react-server-dom-turbopack, and react-server-dom-webpack (versions 19.0.0-19.0.4, 19.1.0-19.1.5, 19.2.0-19.2.4). Next.js versions affected (using App Router): 13.x, 14.x, 15.x (15.0.0 to <15.5.15), 16.x (16.0.0 to <16.2.3). Upgrade to patched versions: Next.js 15.5.15+, 16.2.3+. Note: Next.js 13.x and 14.x are EOL with no patches planned.

Citations:

🌐 Web query:

What is the latest version of eslint-config-next package for Next.js 16.2.3?

💡 Result:

The latest version of the eslint-config-next package is 16.2.3, which matches Next.js 16.2.3 and was published 2 days ago (as of 2026-04-10). This package versions in lockstep with Next.js core releases, so for Next.js 16.2.3, use eslint-config-next@16.2.3. The 'latest' tag on npm is currently 16.2.1, but the specific version 16.2.3 is available and appropriate.

Citations:

Update eslint-config-next to match Next.js 16.2.3.

CVE-2026-23869 (CVSS 7.5) is a high-severity DoS vulnerability in React Server Components affecting Next.js 16.0.0 to <16.2.3. The upgrade to 16.2.3 on line 28 is essential. However, eslint-config-next on line 41 remains at ^16.2.2. Since version 16.2.3 is now available and these packages are released in lockstep, update eslint-config-next to ^16.2.3:

Suggested fix 
-    "eslint-config-next": "^16.2.2",
+    "eslint-config-next": "^16.2.3",
🤖 Prompt for AI Agents 
Verify each finding against the current code and only fix it if needed.

In `@package.json` at line 28, package.json declares "next": "^16.2.3" but still
pins "eslint-config-next" at "^16.2.2", causing a mismatch and leaving
CVE-2026-23869 unaddressed; update the "eslint-config-next" dependency to
"^16.2.3" so it matches the Next.js release series (modify the
"eslint-config-next" entry in package.json), then run your lockfile update
(npm/yarn/pnpm install) and verify tests/linters succeed.

"prisma": "^7.6.0",
"react": "^19.2.4",
"react-dom": "^19.2.4",
Expand Down
Loading