next
16.4.5 · 3 Nov 2026MIT98.4M / weekRepositoryHomepagenpmAtom feed
Upgrading next From 16.0.3 to 16.4.6
45 releases in betweennotes for 43
Counted from 43 of 45 release notes. Advisories are counted from the advisory database, in full.
Start here
Before you upgrade
Tick each one off as you go- Breaking16.4.0
- Breaking16.4.0
- Breaking16.3.0
- Breaking16.3.0
- Breaking16.3.0
- Breaking16.3.0
- Breaking16.2.0
- Breaking16.2.0
- Breaking16.2.0
- Breaking16.2.0
Security
Fixes 48 advisories affecting 16.0.3
- 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
- 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
- Next.js has information disclosure in development server's Model Context Protocol endpointlow · GHSA-39w2-rjm5-chcv
- Next.js's Middleware / Proxy redirects can be cache-poisonedlow · GHSA-3g8h-86w9-wvmq
- Next.js: Unbounded next/image disk cache growth can exhaust storagemoderate · GHSA-3x4c-7xq6-9pq8
- Next.js: Cache confusion of response bodies for requests with bodies containing invalid UTF-8 byte sequencesmoderate · GHSA-4633-3j49-mh5q
- Next.js has a Middleware / Proxy bypass through dynamic route parameter injectionhigh · GHSA-492v-c6pp-mqqv
- Next.js: Unbounded Server Action payload in Edge runtimemoderate · GHSA-4c39-4ccg-62r3
- Next.js has cache poisoning of SSG and ISR pages in self-hosted applicationsmoderate · GHSA-4jqv-mc3x-m676
- Next.js has Unbounded Memory Consumption via PPR Resume Endpoint moderate · GHSA-5f7q-jpqc-wp7h
- Next.js: Unauthenticated Remote Code Execution in `use cache` functions returning typed arrayscritical · GHSA-673q-mjm6-r5xr
- Next.js: Cache confusion of response bodies for requests with bodiesmoderate · GHSA-68g3-v927-f742
- Next.js: Middleware / Proxy bypass in App Router applications using Turbopack and single localehigh · GHSA-6gpp-xcg3-4w24
- Next.js: SVG rejection bypass in the image optimizationmoderate · GHSA-7qx7-33qx-rqx2
- Next.js: Server-Side Request Forgery in Server Actions on custom servershigh · GHSA-89xv-2m56-2m9x
- Next.js Vulnerable to Denial of Service with Server Componentshigh · GHSA-8h8q-6873-q5fj
- Next.js: Unauthenticated disclosure of internal Server Function endpointsmoderate · GHSA-955p-x3mx-jcvp
- Next.js self-hosted applications vulnerable to DoS via Image Optimizer remotePatterns configurationmoderate · GHSA-9g9p-9gw9-jx7f
- Next.js is vulnerable to RCE in React flight protocolcritical · GHSA-9qr9-h5gf-34mp
- Next.js vulnerable to server-side request forgery in applications using WebSocket upgradeshigh · GHSA-c4j6-fc7j-m34r
- Next.js has Server-Side Request Forgery in Image Optimizationhigh · GHSA-cjq9-62q9-8jv4
- Next.js: HttpOnly cookie exposure through internal response header on Next.js Edge runtime routesmoderate · GHSA-f3mh-rxg3-f5g2
- Next.js has information disclosure in App Router metadata image routes via dynamicParams bypassmoderate · GHSA-f87g-xv8r-7p7x
- Next.js vulnerable to cross-site scripting in App Router applications using CSP noncesmoderate · GHSA-ffhc-5mcf-pf4q
- Next.js: HTTP request smuggling in rewritesmoderate · GHSA-ggv3-7p47-pfv8
- Next.js has cross-site scripting in beforeInteractive scripts with untrusted inputmoderate · GHSA-gx5p-jg67-6x7h
- Next.js HTTP request deserialization can lead to DoS when using insecure React Server Componentshigh · GHSA-h25m-26qc-wcjf
- Next.js: Unbounded postponed resume buffering can lead to DoSmoderate · GHSA-h27x-g6w4-24gq
- Next.js has a Denial of Service in the Image Optimization APImoderate · GHSA-h64f-5h5j-jqjh
- Next.js: null origin can bypass dev HMR websocket CSRF checkslow · GHSA-jcc7-9wpm-mj36
- Next.js: Denial of Service in App Router using Server Actionshigh · GHSA-m99w-x7hq-7vfj
- Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of servicemoderate · GHSA-mcj8-r9mp-w47p
- Next.js vulnerable to Denial of Service via connection exhaustion in applications using Cache Componentshigh · GHSA-mg66-mrh9-m8jx
- Next.js: null origin can bypass Server Actions CSRF checksmoderate · GHSA-mq59-m269-xvcx
- Next Vulnerable to Denial of Service with Server Componentshigh · GHSA-mwv6-3258-q52c
- Next.js: Unauthenticated Remote Code Execution on windows-hosted serverscritical · GHSA-p293-qw3h-jr36
- Next.js: Denial of Service in App Router using Server Actionshigh · GHSA-p3m5-59mp-jv5r
- Next.js: Server-Side Request Forgery in rewrites via attacker-controlled destination hostnamehigh · GHSA-p9j2-gv94-2wf4
- Next.js: Cross-client response injection and disclosure in self-hosted Next.js applications forwarding fetched responsesmoderate · GHSA-pc58-hwjq-p385
- Next.js has a Denial of Service with Server Componentshigh · GHSA-q4gf-8mx6-v5v3
- Next.js: Denial of Service in the Image Optimization API using SVGsmoderate · GHSA-q8wf-6r8g-63ch
- Next.js: Cross-user cache disclosure and poisoning in Next.js use cache with binary argumentsmoderate · GHSA-rhh4-g77r-r9qj
- Next.js vulnerable to cache poisoning via collisions in React Server Component cache-bustinglow · GHSA-vfv6-92ff-j949
- Next Server Actions Source Code Exposure moderate · GHSA-w37m-7fhw-fmv9
- Next.js vulnerable to cache poisoning in React Server Component responsesmoderate · GHSA-wfc6-r584-vfw7
- 16.4.5
- 16.4.5
- 16.4.5
- 16.4.5
- 16.4.5
- 16.4.5
- 16.4.5
- 16.4.1
- 16.4.1
- 16.4.1
Release by release
16.4.6nothing new or fixed in the note
- Security
- Security
- Security
- Security
- Security
- Security
- Security
- Fixed
analyze: Use route summaries as the analyzer route index
- Fixed
- Fixed
Fix extensionless Google font URLs in both bundlers
- Fixed
Don't load the app-page runtime in proxy.ts
- Fixed
Avoid loading standalone React in server bootstrap
- Fixed
- Fixed
next-code-frame: Snap visible window to char boundaries
- Fixed
Fix two GC paths that leave half-torn-down dependency edges
- Fixed
Fix Turbopack lazy dynamic-import chunk-list collisions
- Fixed
- Breaking
Remove
config.experimental.appNewScrollHandler - Breaking
Remove
truefromagentUpgradeoption - Deprecated
Pages Router: Deprecate React 18 support
- New
turbopack: Support
falsevalues forresolveAliasconfig
- Breaking
- Security
- Security
- Security
- Security
- Security
- Security
- Security
918 other lines we could not sort, mostly version bumps
- 16.4.6
Pin Tailwind to 4.3.3 in create-next-app and tests (#101061, #101176)
- 16.4.6
Automatically compress route handler responses if not already compressed
- 16.4.6
Turbopack GC fixes for dev (#100279, #100370)
- 16.4.4
Reload on missed Turbopack startup CSS updates
- 16.4.4
Revert "Optimize strict module factory chunks (#98421)"
- 16.4.4
Emit the Turbopack shared-runtime bootstrap in the PPR resume so it gets the CSP nonce
- 16.4.4
Use fast-jwt instead of jsonwebtoken
- 16.4.3
Revert "Turbopack: loader change invalidation (#95732)"
- 16.4.3
Keep OpenTelemetry request traces together (#100349, #100294, #100324, #100350, #100552, #100583)
- 16.4.2
turbo-tasks snapshot consistency fixes (#99644, #99732, #99649)
1925 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.