Authorization Bypass in Next.js Middleware
vercel next.js
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| next npm |
|
|
vercel next.js
| Product | Affected | Fixed in |
|---|---|---|
| next npm |
|
|
Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. 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. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3.
From the CVE record · GitHub_M
Next.js applications are vulnerable when they perform authorization checks in middleware. An external attacker can send a request containing the x-middleware-subrequest header to bypass those checks; no user interaction is described.
Teams running Next.js versions from 1.11.4 up to the applicable fixed release—12.3.5, 13.5.9, 14.2.25, or 15.2.3—should check their applications.