NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-44573: Next.js has a Middleware / Proxy bypass in Pages Router applications using i18n

highCVSS 3.1 7.5GHSA-36qx-fr4f-26g5

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/ / .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.

Published May 11, 2026 · Updated May 14, 2026

Affected packages

next

Ecosystem
npm
Affected
>= 12.2.0, < 15.5.16
Fixed in
15.5.16
Check
npm ls next

next

Ecosystem
npm
Affected
>= 16.0.0, < 16.2.5
Fixed in
16.2.5
Check
npm ls next

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries