If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed.
This issue was patched in Next.js 14.2.15
and later.
If your Next.js application is hosted on Vercel, this vulnerability has been automatically mitigated, regardless of Next.js version.
There are no official workarounds for this vulnerability.
We'd like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.
{ "nvd_published_at": "2024-12-17T19:15:06Z", "cwe_ids": [ "CWE-285" ], "severity": "HIGH", "github_reviewed": true, "github_reviewed_at": "2024-12-17T15:09:06Z" }