Next.js 14.2.25 is a minor release building upon the solid foundation of version 14.2.24. While the core React framework functionality remains consistent, developers will find subtle yet impactful changes, mainly centered around internal dependencies and bug fixes. Both versions share the same core dependencies like busboy, @next/env, and styled-jsx, ensuring a seamless transition for most users.
The key difference lies in the updated @next/swc version, reflecting potential improvements and bug fixes within the Rust-based compiler. This impacts build times and overall performance, which is a crucial factor for developers. Furthermore, the @next/polyfill-module and @next/polyfill-nomodule dependencies are version-bumped in the newer release, indicating adjustments in polyfill handling for modern and legacy browsers.
Developers should also note the releaseDate, which is significantly in the future. The newer version exhibits a small increase in unpackedSize, possibly due to added code or updated dependencies. While the vast majority of devDependencies and peerDependencies remain identical, it's always recommended to review the detailed changelog or release notes for a comprehensive understanding of all changes and potential breaking points relevant to specific project setups. Upgrading from 14.2.24 should be straightforward for most projects, providing a refined and optimized Next.js experience. The core benefit would be in security and potentially improved performance, but it's important to test thoroughly.
All the vulnerabilities related to the version 14.2.25 of the package
Next.js may leak x-middleware-subrequest-id to external hosts
In the process of remediating CVE-2025-29927, we looked at other possible exploits of Middleware. We independently verified this low severity vulnerability in parallel with two reports from independent researchers.
Learn more here.
Thank you to Jinseo Kim kjsman and RyotaK (GMO Flatt Security Inc.) with takumi-san.ai for the responsible disclosure. These researchers were awarded as part of our bug bounty program.
Information exposure in Next.js dev server due to lack of origin verification
A low-severity vulnerability in Next.js has been fixed in version 15.2.2. This issue may have allowed limited source code exposure when the dev server was running with the App Router enabled. The vulnerability only affects local development environments and requires the user to visit a malicious webpage while npm run dev is active.
Because the mitigation is potentially a breaking change for some development setups, to opt-in to the fix, you must configure allowedDevOrigins in your next config after upgrading to a patched version. Learn more.
Learn more: https://vercel.com/changelog/cve-2025-48068
Thanks to sapphi-red and Radman Siddiki for responsibly disclosing this issue.
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
