Headline
GHSA-7gfc-8cq8-jh5f: Next.js authorization bypass vulnerability
Impact
If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application’s root directory. For example:
- [Not affected]
https://example.com/
- [Affected]
https://example.com/foo
- [Not affected]
https://example.com/foo/bar
Patches
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.
Workarounds
There are no official workarounds for this vulnerability.
Credits
We’d like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.
Impact
If a Next.js application is performing authorization in middleware based on pathname, it was possible for this authorization to be bypassed for pages directly under the application’s root directory. For example:
- [Not affected] https://example.com/
- [Affected] https://example.com/foo
- [Not affected] https://example.com/foo/bar
Patches
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.
Workarounds
There are no official workarounds for this vulnerability.
Credits
We’d like to thank tyage (GMO CyberSecurity by IERAE) for responsible disclosure of this issue.
References
- GHSA-7gfc-8cq8-jh5f
- vercel/next.js@1c8234e