next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 14.2.2 to 14.2.3
1 release in betweenevery note read
- 0
- changes to make
- 0
- advisories fixed
- 0
- new
- 7
- fixes
Security
37 advisories still affect 14.2.3
- 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
- Fixed
Resolve mixed re-exports module as cjs
- Fixed
Mixing namespace import and named import client components
- Fixed
Fix mixed exports in server component with barrel optimization
- Fixed
Fix next/image usage in mdx
- Fixed
Prevent erroneous route interception during lazy fetch
- Fixed
Fix root page revalidation when redirecting in a server action
- Fixed
Remove traceparent from cachekey should not remove traceparent from original object
- Fixed
1 other line we could not sort, mostly version bumps
- 14.2.3
Clean-up fetch metrics tracking
1 internal line (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.