fix(security): bump website next to 16.2.6 (5 advisories)#398
fix(security): bump website next to 16.2.6 (5 advisories)#398Sergentval wants to merge 1 commit into
Conversation
Patches the May 2026 Next.js advisory cluster (5 CVEs disclosed 2026-05-06/07). Bumping to 16.2.6 covers all of them: - GHSA-267c-6grr-h53f (HIGH) — Middleware/proxy bypass via segment-prefetch routes (CVSS 8.6 SSRF). Self-hosted only; Vercel-hosted apps unaffected by this one. - GHSA-26hh-7cqf-hhc6 (HIGH) — Same vector, "Incomplete Fix Follow-Up". Requires 16.2.6 specifically. - GHSA-ffhc-5mcf-pf4q (MEDIUM) — XSS via CSP nonces in App Router. - GHSA-gx5p-jg67-6x7h (MEDIUM) — XSS via beforeInteractive scripts. - GHSA-vfv6-92ff-j949 (LOW) — RSC cache poisoning via collisions. Previous pin: ^16.2.4 (lockfile resolved to 16.2.4 — vulnerable to all five). New pin: ^16.2.6.
|
@Sergentval is attempting to deploy a commit to the rohitg00's projects Team on Vercel. A member of the Team first needs to authorize it. |
📝 WalkthroughWalkthroughThe ChangesNext.js Version Bump
Estimated code review effort🎯 1 (Trivial) | ⏱️ ~1 minute Possibly related PRs
Poem
🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
⚔️ Resolve merge conflicts
Tip 💬 Introducing Slack Agent: The best way for teams to turn conversations into code.Slack Agent is built on CodeRabbit's deep understanding of your code, so your team can collaborate across the entire SDLC without losing context.
Built for teams:
One agent for your entire SDLC. Right inside Slack. Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
🧹 Nitpick comments (1)
website/package.json (1)
15-15: Next.js 16.2.6 security update confirmed and compatible. The release (May 7, 2026) addresses critical vulnerabilities including the listed advisories and is fully compatible with React 19.2.5. For complete mitigation of React Server Components vulnerabilities, consider also updating React to 19.2.6 per the official security advisory.🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In `@website/package.json` at line 15, The package.json currently pins "next": "^16.2.6" (safe) but the advisory recommends also updating React; update the react and react-dom entries in package.json to "^19.2.6" (matching the Next.js compatibility note), then regenerate the lockfile (run npm/yarn install) and run the app/tests to ensure no breakage; check the dependencies "next", "react", and "react-dom" in package.json and verify the lockfile changes and CI pass.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Nitpick comments:
In `@website/package.json`:
- Line 15: The package.json currently pins "next": "^16.2.6" (safe) but the
advisory recommends also updating React; update the react and react-dom entries
in package.json to "^19.2.6" (matching the Next.js compatibility note), then
regenerate the lockfile (run npm/yarn install) and run the app/tests to ensure
no breakage; check the dependencies "next", "react", and "react-dom" in
package.json and verify the lockfile changes and CI pass.
ℹ️ Review info
⚙️ Run configuration
Configuration used: defaults
Review profile: CHILL
Plan: Pro
Run ID: 0eb3586d-9e2e-4dde-a5a2-54a5afce1160
⛔ Files ignored due to path filters (1)
website/package-lock.jsonis excluded by!**/package-lock.json
📒 Files selected for processing (1)
website/package.json
Summary
Bumps
website/nextfrom^16.2.4(lockfile pinned to16.2.4) to^16.2.6to patch the five Next.js advisories disclosed 2026-05-06/07.Why
Lockfile-resolved
next@16.2.4is in the vulnerable range for all of:beforeInteractivescripts16.2.6is the smallest bump that covers all five.The README states the website deploys to Vercel, which means the SSRF (
GHSA-267c-6grr-h53f/-26hh-7cqf-hhc6) is already mitigated at the platform layer. The XSS and cache-poisoning advisories still apply to Vercel-hosted apps, so the bump is meaningful regardless.Changes
website/package.json—next: ^16.2.4→^16.2.6website/package-lock.json— regenerated vianpm install --package-lock-only. Resolved version:16.2.6.Test plan
cd website && npm install && npm run build— verify clean build with new dependency treenpm run devand confirm the site rendersnpm auditshould report 0 high/criticalSummary by CodeRabbit