Next.js version 15.3.4 introduces subtle refinements and upgrades compared to its predecessor, 15.3.3, targeting enhanced developer experience and optimized performance. While the core framework structure remains consistent, evidenced by shared dependencies like busboy, postcss, and @swc/helpers, the key changes lie in the version bumps of @next packages and potential bug fixes.
Developers will notice that @next/env, @next/font, @next/polyfill-module, @next/polyfill-nomodule, @next/react-refresh-utils, @next/swc-darwin-x64, @next/swc-darwin-arm64, @next/swc-linux-x64-gnu, @next/swc-linux-x64-musl, @next/swc-win32-x64-msvc, @next/swc-linux-arm64-gnu, @next/swc-linux-arm64-musl, @next/swc-win32-arm64-msvc and @next/swc are updated. These increments suggest improvements across environment variable handling, font optimization, polyfilling functionalities, React Fast Refresh integration, and SWC-related features, potentially bringing faster builds and improved runtime behavior.
The update includes storybook to version 8.6, with updated dependencies to work with it, such as @storybook/react, @storybook/blocks, @storybook/addon-interactions, @storybook/addon-essentials, @storybook/react-webpack5, @storybook/addon-webpack5-compiler-swc and @storybook/addon-a11y.
Developers should carefully review the changelog for specific details and potential breaking changes associated with these updated packages. The releaseDate suggests the update may contains temporal features to be released in june. The slight difference in unpacked size also points to internal adjustments and optimizations bundled within the new version, making 15.3.4 a recommended upgrade for those seeking the latest enhancements and stability improvements within the Next.js ecosystem.
All the vulnerabilities related to the version 15.3.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
