next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 14.2.3 to 14.2.4
1 release in betweenevery note read
Security
37 advisories still affect 14.2.4
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are usedcritical · GHSA-2464-fhr4-w9xw
- Next.js: Unauthenticated Remote Code Execution in Image Optimization API when AVIF files are usedcritical · GHSA-2xp9-vwfh-vxw4
- Next.js has a Middleware / Proxy bypass in Pages Router applications using i18nhigh · GHSA-36qx-fr4f-26g5
Upgrading to 15.5.29 clears them.
Release by release
- New
Add timeout/retry handling for fetch cache
- Fixed
Ensure route handlers properly track dynamic access
- Fixed
Fix NextRequest proxy in edge runtime
- Fixed
Fix next/dynamic with babel and src dir
- New
2 other lines we could not sort, mostly version bumps
- 14.2.4
Use vercel deployment url for metadataBase fallbacks
- 14.2.4
Use addDependency to track metadata route file changes
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.