next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 16.2.0 to 16.2.1
1 release in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 4
- fixes
Security
39 advisories still affect 16.2.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
- Fixed
Fix adapter outputs for dynamic metadata routes
- Fixed
Turbopack: Fix webpack loader runner layer
- Fixed
Fix server actions in standalone mode with
cacheComponents - Fixed
Fix layout segment optimization: move app-page imports to server-utility transition
- Fixed
3 other lines we could not sort, mostly version bumps
- 16.2.1
turbo-persistence: Remove Unmergeable mmap advice
- 16.2.1
Turbopack: Lazy require metadata and handle TLA
- 16.2.1
Respect
{eval:true}in worker_threads constructors
2 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.