CVE-2026-44573: Next.js Pages Router i18n Middleware Authorization Bypass
- Vendor
- Vercel
CVE-2026-44573 is an authorization bypass in Next.js Pages Router applications configured with internationalization (i18n) and middleware/proxy-based authorization. Middleware matcher logic fails to associate locale-less internal page-data requests with their logical page routes, causing authorization checks to be skipped and exposing protected server-side rendered JSON. Affected versions are 12.2.0 through 15.5.15 and 16.0.0 through 16.2.4. Applications using the App Router, or the Pages Router without i18n, are not affected by this specific vulnerability.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Unauthenticated remote attackers can retrieve protected server-side rendered page data without passing middleware-based authorization. Exposed JSON can include properties generated by getServerSideProps or equivalent server-side data fetching functions, potentially disclosing dashboard, administrative, or internal application data.
Mitigation
If you can’t patch tonight, do this now.
If upgrading immediately is not possible, enforce authorization within getServerSideProps or another server-side data-fetching path rather than relying solely on middleware or proxy authorization. WAF rules were not deployed for this vulnerability class because it cannot be reliably blocked at that layer; upgrading remains the complete remediation.
Remediation
Patch, then assume compromise.
Upgrade Next.js to a patched release: 15.5.16 or later on the 15.x branch, or 16.2.5 or later on the 16.x branch. Earlier affected branches require migration to a fixed release. Recommended patched releases include 15.5.18 and 16.2.6. The fix normalizes locale-less data requests to their logical page paths before middleware matching, ensuring authorization middleware executes consistently.
Exploits
No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-44573 exploited in the wild?
- As of Oct 3, 2026, Mallory has no reports of CVE-2026-44573 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-44573?
- As of Oct 3, 2026, Mallory has not confirmed a public exploit for CVE-2026-44573. 1 candidate exploit record is not yet analyzed.
- Is there a patch for CVE-2026-44573?
- Upgrade Next.js to a patched release: 15.5.16 or later on the 15.x branch, or 16.2.5 or later on the 16.x branch. Earlier affected branches require migration to a fixed release.
- What products are affected by CVE-2026-44573?
- Vercel Next.Js.
- How severe is CVE-2026-44573?
- CVE-2026-44573 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 0.80% (57th percentile) as of Oct 3, 2026.
Recent activity
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.