next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 15.2.2 to 15.2.3
1 release in betweenevery note read
- 0
- changes to make
- 1
- advisory fixed
- 1
- new
- 2
- fixes
Security
40 advisories still affect 15.2.3
- Next.js may leak x-middleware-subrequest-id to external hostslow · GHSA-223j-4rm8-mrmf
- 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
Upgrading to 15.5.29 clears them.
Fixes 1 advisory affecting 15.2.2
- Authorization Bypass in Next.js Middlewarecritical · GHSA-f82v-jwr5-mffw
- 15.2.3
This release contains a security patch for CVE-2025-29927.
Release by release
- Security
This release contains a security patch for CVE-2025-29927.
- New
Add dev warning for cross-origin and stabilize allowedDevOrigins
- Fixed
Ensure deploymentId is used for CSS preloads
- Fixed
Fix vscode type hint plugin enabling
- Security
5 other lines we could not sort, mostly version bumps
- 15.2.3
Update default allowed origins list
- 15.2.3
Unify allowed origin detection handling
- 15.2.3
Update middleware request header
- 15.2.3
Remove the default segement check for metadata rendering
- 15.2.3
re-insert icons to head for streamed metadata
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.