Skip to main content
Live Webinar with SANS (June 25)— Agentic CTI Automation for Fun & ProfitRegister Free
Mallory
High

Next.js App Router segment-prefetch middleware bypass

IdentifiersCVE-2026-44575CWE-285

CVE-2026-44575 is an authorization bypass in Next.js App Router applications. In affected versions from 15.2.0 before 15.5.16, and in the 16.x branch before 16.2.5, applications that depend on middleware or proxy-based authorization checks can be bypassed through transport-specific route variants used for segment prefetching. Specially crafted .rsc and segment-prefetch URLs can resolve to the same underlying page while not matching the intended middleware rule, causing the request to reach protected content without the expected authorization check. The issue affects authorization logic implemented only at the middleware/proxy layer rather than in the route or page handler itself.

Share:
For your environment

Are you exposed to this one?

Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.

ANALYST BRIEF

Impact, mitigation & remediation

What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.

Impact

What an attacker gets, and what they’ve been doing with it.

Successful exploitation can allow unauthorized access to protected App Router content. An attacker may retrieve pages or resources that should have been gated by middleware or proxy authorization checks by requesting transport-specific route variants that resolve to the same page but evade the configured matcher. The primary impact is access-control bypass and exposure of protected content.

Mitigation

If you can’t patch tonight, do this now.

If immediate patching is not possible, do not rely solely on middleware or proxy-based authorization for sensitive App Router routes. Enforce authorization checks in the underlying route, page, or server-side application logic so that access control is validated regardless of transport-specific URL variants such as .rsc or segment-prefetch requests.

Remediation

Patch, then assume compromise.

Upgrade Next.js to a fixed release. The vulnerability is fixed in 15.5.16 for the 15.x branch and 16.2.5 for the 16.x branch. Apply the upstream fix so middleware matchers correctly account for App Router transport variants used during segment prefetching.
PUBLIC EXPLOITS

Exploits

No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.

VALID 0 / 1 TOTALView more in app

All candidate exploits were filtered out by Mallory's validation.

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
VercelNextapplication
VercelNext.Jsapplication

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

ACTIVITY FEED

Recent activity

9 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.

No news coverage yet. Advisories and community discussion only.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence

Every observed campaign linking this CVE to a named adversary.

Associated malware

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity9

Community discussion across Reddit, Mastodon, and other social sources.