Skip to main content
Mallory
HighVulnerability

CVE-2026-44573: Next.js Pages Router i18n Middleware Authorization Bypass

Published May 13, 2026 · Updated 2 months ago
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 daysNo mention activity in the last 30 days.
CVSS7.5High · v3.1
EPSS0.80%57th percentile
CISA KEVNoNot listed
In the wildNoneNo exploitation reported
Vendor
Vercel
IdentifiersCVE-2026-44573CWE-863 · Incorrect Authorization

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

Exploits

No validated public exploits yet. Hidden: 1 not yet analyzed, such as Exploit-DB entries.

View more in app →
Candidate exploits are awaiting analysis. View them in Mallory.
Exposure surface

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.

VendorProductType
VercelNext.Jsapplication
FAQ

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.
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidenceEvery report linking this CVE to a named adversary.
Associated malwareMalware families linked to this CVE, with evidence and IOCs.
Detection signaturesYARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity8Community discussion across Reddit, Mastodon, and other social sources.