Next.js is a React framework for building full-stack web applications. In versions 16.0.0 through 16.2.10, crafted requests targeting Next.js applications using App Router built with Turbopack and a single entry in config.i18n.locales can bypass middleware/proxy based authentication. This issue has been fixed in version 16.2.11.
Fix
Patch, vendor advisory and mitigation references on NVD 3
- https://github.com/vercel/next.js/commit/6bf4df14508ad6c0cd46af50c6051ee42f2d9151 Patch
- https://github.com/vercel/next.js/pull/96014 Issue Tracking, Patch
- https://github.com/vercel/next.js/security/advisories/GHSA-6gpp-xcg3-4w24 Vendor Advisory
Every line above is quoted from NVD, CISA, Microsoft, the vendor's own advisory or DISA; nothing is generated.
Change history 1
- First seenCVSS 8.3 · vercelNVD modified 2026-10-24 13:10
Affected (CPE criteria) 1
cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:*
References 4
- https://github.com/vercel/next.js/commit/6bf4df14508ad6c0cd46af50c6051ee42f2d9151 Patch
- https://github.com/vercel/next.js/pull/96014 Issue Tracking, Patch
- https://github.com/vercel/next.js/releases/tag/v16.2.11 Product, Release Notes
- https://github.com/vercel/next.js/security/advisories/GHSA-6gpp-xcg3-4w24 Vendor Advisory