Next.js version 14.2.30 introduces subtle but important updates compared to its predecessor, 14.2.29. Both versions share the same core React framework capabilities and identical dependency baselines for core functionality, including React, React DOM, and crucial tools like PostCSS, Styled-JSX and @swc/helpers. Their peer dependencies, such as Sass and @opentelemetry/api, also remain consistent, aiming for backward compatibility and stability in your existing projects.
The key differences primarily reside in the updated versions of internal Next.js modules. Notably, @next/env, @next/swc, @next/polyfill-module, @next/polyfill-nomodule, @next/react-refresh-utils as well as optional dependencies such as @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-win32-ia32-msvc, @next/swc-linux-arm64-musl, @next/swc-win32-arm64-msvc have been bumped to 14.2.30. These updates likely contain bug fixes, performance improvements, and potentially new features within the Next.js ecosystem. The fileCount and unpackedSize have also changed slightly, potentially reflecting changes to assets and compiled code.
Developers upgrading to 14.2.30 should anticipate minor potential improvements in areas like environment variable handling, SWC-based compilation, polyfilling, and React Fast Refresh. Examine the Next.js changelog and release notes in order to confirm changes.
All the vulnerabilities related to the version 14.2.30 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
