Repository navigation
fix(www): update next to 16.4.6 for two 'use cache' advisories - #220
Conversation
…-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>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Updates the site's
nextfrom 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:
'use cache'functions.'use cache'function is called…The site uses
'use cache'throughout its data layer (apps/www/src/lib/data.ts).next buildon 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:nextspec^16.3.8→^16.4.5.vlt-lock.json: written byvlt install -w apps/www 'next@^16.4.5', run with no user config. The only version changes arenextand@next/*(16.4.2 → 16.4.6). Every other package keeps its version; the remaining diff lines are peer-context IDs that reference thenextnode.Verified
vlr format:check,vlr lint:check,vlr typecheck: clean.apps/www:vlr test277 passed.next buildagainsthttps://benchmarks-data.vlt.io: exit 0 on the first try, 40/40 pages, no security gate.🤖 Generated with Claude Code
Summary by CodeRabbit