next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 15.2.1 to 15.2.2
1 release in betweenevery note read
- 0
- changes to make
- 1
- advisory fixed
- 3
- new
- 16
- fixes
Security
40 advisories still affect 15.2.2
- 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.
Fixes 1 advisory affecting 15.2.1
- Information exposure in Next.js dev server due to lack of origin verificationlow · GHSA-3h52-269p-cp9r
Release by release
- New
Add types for
__next_app__module loading functions - New
Turbopack: Add turbopack_load_by_url
- New
Add handling of origin in dev mode
- Fixed
Fix styling on overflow error messages, add button hover state
- New
7 other lines we could not sort, mostly version bumps
- 15.2.2
Always show relative paths
- 15.2.2
Remove the duplicate metadata in the error boundary
- 15.2.2
Ignore animations on page load
- 15.2.2
dev-overlay: Remove dependency on platform for focus trapping
- 15.2.2
Increase padding if no
xbutton present - 15.2.2
Dim ignore-listed callstack frames when shown
- 15.2.2
Revert "fix(turbopack): Use vergen-git2 instead of shadow-rs for napi and next-api crates to fix stale git lock files"
34 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.