Skip to content

fix(www): update next to 16.4.6 for two 'use cache' advisories - #220

Merged
lukekarrys merged 1 commit into
mainfrom
lk/next-16.4.5
Nov 18, 2026
Merged

lukekarrys merged 1 commit into
mainfrom
lk/next-16.4.5

Conversation

@lukekarrys

@lukekarrys lukekarrys commented Nov 18, 2026 •

Copy link
Copy Markdown
Member

Updates the site's next from 16.4.2 to 16.4.6.

Why

16.4.2 is in the vulnerable range of two moderate advisories published 2026-11-16 and 2026-11-17, both fixed in 16.4.5:

  • GHSA-vc7v-qv4w-wrv8: cache leak across root param values in nested 'use cache' functions.
  • GHSA-mfr8-8qww-v76h: information disclosure across root params when a 'use cache' function is called…

The site uses 'use cache' throughout its data layer (apps/www/src/lib/data.ts). next build on 16.4.2 also stopped with Next's own "known security vulnerability" gate (seen in several builds on 2026-11-18).

Change

  • apps/www/package.json: next spec ^16.3.8 → ^16.4.5.
  • vlt-lock.json: written by vlt install -w apps/www 'next@^16.4.5', run with no user config. The only version changes are next and @next/* (16.4.2 → 16.4.6). Every other package keeps its version; the remaining diff lines are peer-context IDs that reference the next node.

Verified

  • vlr format:check, vlr lint:check, vlr typecheck: clean.
  • apps/www: vlr test 277 passed.
  • next build against https://benchmarks-data.vlt.io: exit 0 on the first try, 40/40 pages, no security gate.

🤖 Generated with Claude Code

Summary by CodeRabbit

  • Chores
    • Updated the web app’s underlying framework and related package resolutions. No user-facing changes are included in this update.

…-8qww-v76h

next 16.4.2 is in the vulnerable range of two moderate advisories
published 2026-11-16/17: cache leaks and information disclosure across
root param values in 'use cache' functions, which the site uses
throughout. Both are fixed in 16.4.5. `next build` also stops with
Next's "known security vulnerability" gate on 16.4.2.

Lockfile written by `vlt install` (no user config); only next and
@next/* change version.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@vercel

vercel Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
benchmarks Ready Ready Preview Nov 18, 2026 7:33am UTC

Request Review

@coderabbitai

coderabbitai Bot commented Nov 18, 2026 •

Copy link
Copy Markdown

Explain Change →

No actionable comments were generated in the recent review.

Walkthrough

The apps/www Next.js dependency range changed to ^16.4.5. The lockfile resolves Next.js to 16.4.6 and updates related package resolutions and dependency edges.

Changes: Next.js dependency update

Layer / File(s) Summary
Update the app dependency range
apps/www/package.json, vlt-lock.json
The apps/www manifest and its lockfile dependency edge use the Next.js range ^16.4.5.
Refresh Next.js lockfile resolutions
vlt-lock.json
The lockfile resolves Next.js and its support packages to 16.4.6. Related peer-resolution references and dependency edges are updated. Serialized metadata is added to listed @types package nodes.

Estimated code review effort: 2 (Simple) | ~8 minutes

Change: Other

Suggested reviewers: ejkorol

Merge Risk: Minimal · up to 6fb1b

This is a dependency patch update that moves the site to a Next.js version containing the fixes for two advisories involving 'use cache'. No merge-blocking risk was found.

Pre-merge checks: Passed 4

Check name Status Explanation
Description Check Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check Passed The title names the main change: updating the Next.js dependency in apps/www to 16.4.6 to address two 'use cache' security advisories. The raw summary confirms the package.json bump from ^16.3.8 to ^1…
Linked Issues check Passed Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check Passed Check skipped because no linked issues were found for this pull request.
Full details: Title check

Explanation

The title names the main change: updating the Next.js dependency in apps/www to 16.4.6 to address two 'use cache' security advisories. The raw summary confirms the package.json bump from ^16.3.8 to ^16.4.5 and the lockfile move of next from 16.4.2 to 16.4.6. The objectives describe the same advisories and fix. The title is specific, concise, and matches the changeset.

Finishing Touches

Generate unit tests (beta)

  • Commit to this branch
  • Create a new PR
  • Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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.

Share

Recent review info

Run configuration

  • Source mode: Auto
  • Repository: Unavailable
  • Branch: Unavailable
  • File: No configuration file from this repository applied
  • Commit: Unavailable
  • Layers: defaults
  • Review profile: CHILL
  • Plan: Advanced
  • Run ID: 1153397a-7a01-45b4-8775-b24bfed4d0b7
Commits

Reviewing files that changed from the base of the PR and between 48920d2 and 6fb1ba5.

Files selected for processing: 2

  • apps/www/package.json
  • vlt-lock.json

Included review availability: This review used your included allowance. Your plan provides up to 1 included review per hour; 0 remain after this review.

@socket-security

Copy link
Copy Markdown

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff Package Supply Chain
Security
Vulnerability Quality Maintenance License
Updatednext@​16.4.2 ⏵ 16.4.662 +1100 +390 +19970

View full report

@lukekarrys
lukekarrys merged commit 57e8062 into main Nov 18, 2026
78 checks passed
@lukekarrys
lukekarrys deleted the lk/next-16.4.5 branch November 18, 2026 07:55

This branch was previously deployed

1 inactive deployment
Benchmark — 6fb1ba5d Deployed Nov 18, 2026 by lukekarrys via Run Benchmarks (run, run) #1457
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant