Next.js version 15.4.4 introduces subtle refinements over its predecessor, 15.4.3, focusing primarily on internal dependencies and build processes rather than groundbreaking feature additions. For developers, this translates to enhanced stability and potentially minor performance improvements under the hood, although direct functional changes might be imperceptible. The core dependencies like postcss, @next/env, styled-jsx, @swc/helpers, and caniuse-lite remain consistent, ensuring compatibility and similar behavior for core styling and environment handling.
A key difference lies in the @next/react-refresh-utils package, updated from 15.4.3 to 15.4.4, suggesting tweaks in React Fast Refresh capabilities, potentially impacting the developer experience during local development with faster updates. Several of the optional @next/swc-* packages have also been updated. While the extensive list of devDependencies appears largely the same between versions, even minor version bumps within these tools (such as build tools, testing frameworks, and type definitions) can contribute to a more streamlined development workflow and more reliable builds. The release date also shows that is a really recent update with bug fixes and tiny updates.
Developers should upgrade to 15.4.4 for the latest optimizations and refinements, particularly if they've encountered issues related to React Fast Refresh or desire to benefit from the newest iterations of underlying build and development tools. It’s always beneficial to stay current to receive the latest bug fixes and performance enhancements.
All the vulnerabilities related to the version 15.4.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
