next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 15.5.3 to 15.5.4
1 release in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 6
- fixes
Security
38 advisories still affect 15.5.4
- 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 15.5.29 clears them.
Release by release
- Fixed
Ensure onRequestError is invoked when otel enabled
- Fixed
Devtools initial position should be from next config
- Fixed
Fix overlay styles are missing
- Fixed
Turbopack: Don't match dynamic pattern for node_modules packages
- Fixed
Turbopack: Don't treat metadata routes as RSC
- Fixed
Error overlay not closing when backdrop clicked
- Fixed
3 other lines we could not sort, mostly version bumps
- 15.5.4
Improve handling of symlink resolution errors in track_glob and read_glob
- 15.5.4
Turbopack: Throw large static metadata error earlier
- 15.5.4
Turbopack: Flush Node.js worker IPC on error
3 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.