next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 16.0.0 to 16.0.1
1 release in betweenevery note read
- 1
- change to make
- 0
- advisories fixed
- 0
- new
- 10
- fixes
Before you upgrade
Tick each one off as you go- Breaking16.0.1
Security
48 advisories still affect 16.0.1
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are usedcritical · GHSA-2464-fhr4-w9xw
- Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routeshigh · GHSA-267c-6grr-h53f
- Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes - Incomplete Fix Follow-Uphigh · GHSA-26hh-7cqf-hhc6
Upgrading to 16.4.5 clears them.
Release by release
- Breaking
Remove unstable_forceStale prefetch option & restore
prefetch={true}functionality - Fixed
static-paths: Add depth tracking to parallel route param resolution
- Fixed
Fix types of @next/mdx
- Fixed
Ensure getServerInsertedHTML skips rendering correctly
- Breaking
2 other lines we could not sort, mostly version bumps
- 16.0.1
Exclude
next-jscondition from middleware, proxy, and instrumentation - 16.0.1
Generalize Segment Cache fallback implementation
31 internal lines (docs, tests, tooling) left out.
A whole project to check? Paste its package.json in the dependency check: every deprecated, outdated or vulnerable dependency, with what to upgrade to. Free, no account.