CVE-2026-44575: Next.js App Router Prefetch Middleware Authorization Bypass
- Vendor
- Vercel
CVE-2026-44575 is an authorization bypass in Next.js App Router applications that rely on middleware or proxy-based access controls. Incomplete matcher generation in getMiddlewareMatchers fails to cover certain React Server Components and segment-prefetch transport variants. Crafted requests can therefore resolve to protected pages without matching the intended middleware rule, skipping authorization and returning protected React Server Components payloads. Affected releases include Next.js 15.2.0 through 15.5.15 and 16.0.0 through 16.2.4. Initial fixes were released in 15.5.16 and 16.2.5; an incomplete fix affecting Turbopack configurations is tracked separately as CVE-2026-45109.
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 access protected page content and sensitive data when authorization is enforced solely through bypassed middleware or proxy checks. The primary impact is loss of confidentiality; no direct integrity or availability impact is identified. The vulnerability has a CVSS v3.1 score of 7.5 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N).
Mitigation
If you can’t patch tonight, do this now.
Enforce authorization directly within the underlying route or page logic rather than relying solely on middleware or proxy checks. A Cloudflare managed WAF rule is available but must be enabled manually. WAF filtering should be treated only as supplemental protection because the bypass cannot be reliably blocked at that layer; patching remains necessary.
Remediation
Patch, then assume compromise.
Upgrade Next.js to a patched release. Versions 15.5.16 and 16.2.5 contain the initial fix, which extends generated middleware matchers to cover App Router transport variants. Because that fix was incomplete for middleware built with Turbopack, use 15.5.18 or later in the 15.x line, or 16.2.6 or later in the 16.x line, to address the related CVE-2026-45109 bypass as well. Verify that protected pages and their transport variants consistently enforce authorization after upgrading.
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-44575 exploited in the wild?
- As of Nov 5, 2026, Mallory has no reports of CVE-2026-44575 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-44575?
- As of Nov 5, 2026, Mallory has not confirmed a public exploit for CVE-2026-44575. 1 candidate exploit record is not yet analyzed.
- Is there a patch for CVE-2026-44575?
- Upgrade Next.js to a patched release. Versions 15.5.16 and 16.2.5 contain the initial fix, which extends generated middleware matchers to cover App Router transport variants.
- What products are affected by CVE-2026-44575?
- Vercel Next.Js.
- How severe is CVE-2026-44575?
- CVE-2026-44575 has a CVSS v3.1 score of 7.5 (High) and an EPSS score of 1.6% (76th percentile) as of Nov 5, 2026.
Recent activity
15 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.