CVE-2025-29927: Authorization Bypass in Next.js Middleware
(updated )
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
References
- github.com/advisories/GHSA-f82v-jwr5-mffw
- github.com/vercel/next.js
- github.com/vercel/next.js/commit/52a078da3884efe6501613c7834a3d02a91676d2
- github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48
- github.com/vercel/next.js/releases/tag/v12.3.5
- github.com/vercel/next.js/releases/tag/v13.5.9
- github.com/vercel/next.js/security/advisories/GHSA-f82v-jwr5-mffw
- nvd.nist.gov/vuln/detail/CVE-2025-29927
- security.netapp.com/advisory/ntap-20250328-0002
- vercel.com/changelog/vercel-firewall-proactively-protects-against-vulnerability-with-middleware
Code Behaviors & Features
Detect and mitigate CVE-2025-29927 with GitLab Dependency Scanning
Secure your software supply chain by verifying that all open source dependencies used in your projects contain no disclosed vulnerabilities. Learn more about Dependency Scanning →