Next.js version 15.2.4 is a minor release following 15.2.3, primarily focusing on internal updates and refinements rather than groundbreaking feature additions. Developers considering upgrading will find a familiar landscape, as the core dependencies and development tools largely remain consistent. Both versions share the same foundational dependencies, including busboy, postcss, and the @swc suite, indicating a continuation of the existing performance and styling paradigms.
The key differences lie within the @next/swc packages, which are crucial for compilation and transformation, as well as the peer dependencies and optional dependencies. Upgrading next from 15.2.3 to 15.2.4 brings in the newest built-in compiler and transformer updates ensuring optimal compatibility. The peer dependencies remain the same across both versions.
Developers who depend on edge runtime or experimental features might find subtle improvements and bug fixes related to those areas. Reviewing the Next.js changelog for specific commit details related to these internal packages is highly recommended before upgrading to ensure a smooth transition and avoid potential compatibility issues with custom configurations, especially if heavily reliant on edge features. Ultimately, this incremental update targets stability.
All the vulnerabilities related to the version 15.2.4 of the package
Next.js Affected by Cache Key Confusion for Image Optimization API Routes
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. When images returned from API routes vary based on request headers (such as Cookie or Authorization), these responses could be incorrectly cached and served to unauthorized users due to a cache key confusion bug.
All users are encouraged to upgrade if they use API routes to serve images that depend on request headers and have image optimization enabled.
More details at Vercel Changelog
Next.js Content Injection Vulnerability for Image Optimization
A vulnerability in Next.js Image Optimization has been fixed in v15.4.5 and v14.2.31. The issue allowed attacker-controlled external image sources to trigger file downloads with arbitrary content and filenames under specific configurations. This behavior could be abused for phishing or malicious file delivery.
All users relying on images.domains or images.remotePatterns are encouraged to upgrade and verify that external image sources are strictly validated.
More details at Vercel Changelog
Next.js Improper Middleware Redirect Handling Leads to SSRF
A vulnerability in Next.js Middleware has been fixed in v14.2.32 and v15.4.7. The issue occurred when request headers were directly passed into NextResponse.next(). In self-hosted applications, this could allow Server-Side Request Forgery (SSRF) if certain sensitive headers from the incoming request were reflected back into the response.
All users implementing custom middleware logic in self-hosted environments are strongly encouraged to upgrade and verify correct usage of the next() function.
More details at Vercel Changelog
