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

Published May 11, 2026
·
Updated

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.

Other sources

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.

MITRE

Affected Software

4 affected componentsFixes available
npm/next>=16.0.0<16.2.5
16.2.5
npm/next>=12.2.0<15.5.16
15.5.16
Vercel Next.js Node.js>=12.2.0<15.5.16
Vercel Next.js Node.js>=16.0.0<16.2.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade npm/next to a version that resolves this vulnerability.

    Fixed in 16.2.5
  2. Upgrade

    Upgrade npm/next to a version that resolves this vulnerability.

    Fixed in 15.5.16
  3. Upgrade

    Upgrade Next.js to a version that resolves this vulnerability.

    Fixed in 15.5.16
  4. Upgrade

    Upgrade Next.js to a version that resolves this vulnerability.

    Fixed in 16.2.5
  5. Compensating control

    If you cannot upgrade immediately, enforce authorization in the page's server-side data path instead of relying solely on middleware, because middleware does not run for the unprefixed locale-less /_next/data/<buildId>/<page>.json route.

Event History

May 11, 2026
Advisory Published
via GitHub·03:53 PM
Data Sourced
via GitHub·03:53 PM
DescriptionSeverityWeaknessAffected Software
May 13, 2026
CVE Published
via MITRE·04:48 PM
Data Sourced
via MITRE·04:48 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·05:16 PM
DescriptionSeverityWeaknessAffected Software
Data Sourced
via Red Hat·06:02 PM
DescriptionSeverityAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-44573?

CVE-2026-44573 has a severity rating of 7.5, classified as high.

2

How do I fix CVE-2026-44573?

To mitigate CVE-2026-44573, ensure that middleware is correctly configured to handle locale-based requests in Pages Router applications.

3

What applications are affected by CVE-2026-44573?

Applications using the Pages Router with i18n configured and employing middleware-based authorization are affected by CVE-2026-44573.

4

What is the impact of CVE-2026-44573?

The impact of CVE-2026-44573 is unauthorized access to protected page data through specific locale-less requests.

5

When was CVE-2026-44573 published?

CVE-2026-44573 was published on May 11, 2026.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203