Next.js version 14.2.23 is a minor release, building upon the solid foundation of version 14.2.22. Both versions share the same core dependencies like busboy, postcss, @next/env, and styled-jsx, ensuring backward compatibility for many projects. Most dependencies are identical, indicating an emphasis on stability and refinement rather than radical changes. Key peer dependencies like react, react-dom, @playwright/test, and @opentelemetry/api also remain consistent, meaning upgrades within the React 18 ecosystem should be seamless.
The differences between the versions appear subtle, with only @next/polyfill-module, @next/react-refresh-utils, and @next/swc being updated to 14.2.23 from 14.2.22. This points to focused improvements within Next.js's core modules, potentially involving bug fixes, performance enhancements in hot reloading, or refinements to the SWC compiler integration. File counts and unpacked sizes of the distribution archives are highly similar, suggesting that changes are localized.
For developers, this minor update assures continued stability while incorporating small but potentially impactful internal improvements. Upgrading from 14.2.22 to 14.2.23 should be straightforward, especially for projects already leveraging the latest React features. The core functionality of setting up server rendered React applications, routing, and API handling remain unchanged, allowing developers to continue working with Next.js's established patterns seamlessly. For developers concerned about cutting-edge performance or the latest fixes in React Fast Refresh, this upgrade is highly recommended.
All the vulnerabilities related to the version 14.2.23 of the package
Next.js Race Condition to Cache Poisoning
Summary
We received a responsible disclosure from Allam Rachid (zhero) for a low-severity race-condition vulnerability in Next.js. This issue only affects the Pages Router under certain misconfigurations, causing normal endpoints to serve pageProps data instead of standard HTML.
Credit
Thank you to Allam Rachid (zhero) for the responsible disclosure. This research was rewarded as part of our bug bounty program.
Authorization Bypass in Next.js Middleware
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
15.2.314.2.2513.5.912.3.5Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.
If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application.
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