Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

CAO 7.5CVE-2026-44573 · GHSA-36qx-fr4f-26g5 · Công bố 13/05/2026 · cập nhật 26/10/2026

Gói / sản phẩm	Phiên bản bị ảnh hưởng	Phiên bản đã vá
next.js vercel	`≥ 12.2.0, < 15.5.16≥ 16.0.0, < 16.2.5`	`15.5.1616.2.5`
next npm	`≥ 12.2.0, < 15.5.16≥ 16.0.0, < 16.2.5`	`15.5.1616.2.5`

Mô tả

Impact

Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks.

Fix

The matcher logic was updated to perform the same match as it would on a non-i18n data route.

Workarounds

If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware.

Mô tả của NVD

Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5.