Next.js has released version 14.2.27, incrementally updating from the previous stable version, 14.2.26. The core functionalities and dependencies remain largely consistent, indicating a focus on stability and incremental improvements. Both versions share the same core dependencies like busboy, postcss, @next/env, styled-jsx, graceful-fs, @swc/helpers, and caniuse-lite, ensuring a consistent foundation for Next.js applications. Similarly, the development dependencies, including essential tools like webpack, babel, and testing frameworks, are aligned, suggesting that the development workflow and tooling remain largely unchanged.
The primary distinction lies in the updated @next/swc version and @next/polyfill-module along with the increment in the release date. While seemingly minor, these updates likely contain crucial bug fixes, performance enhancements, and refinements to the Rust-based SWC compiler, which is central to Next.js's build process, and core modules. Developers should prioritize upgrading to 14.2.27 to benefit from these under-the-hood improvements that contribute to a smoother and more efficient development experience. Furthermore, the updated release date signifies ongoing maintenance and commitment to address emerging issues and improve overall stability. Both versions support the same peer dependencies, including React and React DOM, ensuring compatibility with the latest React ecosystem.
All the vulnerabilities related to the version 14.2.27 of the package
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
