CVE-2026-44575: Next.js: Middleware / Proxy bypass in App Router applications via segment-prefetch routes
Next.js is a React framework for building full-stack web applications. From 15.2.0 to before 15.5.16 and 16.2.5, App Router applications that rely on middleware or proxy-based checks for authorization can allow unauthorized access through transport-specific route variants used for segment prefetching. In affected configurations, specially crafted .rsc and segment-prefetch URLs can resolve to the same page without being matched by the intended middleware rule, which can allow protected content to be reached without the expected authorization check. This vulnerability is fixed in 15.5.16 and 16.2.5.
Security readout for executives and security teams
Plain-English summary
Affected Next.js applications may expose protected page content because certain prefetch-related URL variants can bypass middleware or proxy authorization checks. The issue is remotely reachable without credentials or user interaction when the vulnerable application design is present. Confidential information is the primary risk; the supplied evidence does not indicate data modification or service disruption.
Executive priority
Prioritize rapid remediation for internet-facing applications that place confidential content behind middleware or proxy checks. Upgrade affected releases promptly and validate every protected App Router route. Lower priority is reasonable only after confirming the application is outside the affected versions or does not depend on the vulnerable authorization pattern.
Technical view
CVE-2026-44575 affects Next.js App Router versions 15.2.0 through 15.5.15 and 16.0.0 through 16.2.4. Specially crafted .rsc and segment-prefetch routes may resolve to a protected page without matching its intended middleware or proxy rule. CVSS 3.1 is 7.5, reflecting unauthenticated, low-complexity network access and high confidentiality impact.
Likely exposure
Exposure is limited to affected Next.js versions using the App Router where authorization depends on middleware or proxy matching. Applications using other versions, architectures, or independent server-side authorization may not be vulnerable. Internet-facing protected routes and sensitive rendered content increase business risk.
Exploitation context
The supplied record marks this CVE as absent from KEV and provides no evidence of active exploitation. Its network reachability, low complexity, and lack of required credentials make vulnerable deployments attractive targets, but real-world exploit prevalence is unknown from the available sources.
Researcher notes
The weakness is an authorization-check bypass caused by alternate transport-specific routing forms reaching the same resource without equivalent middleware matching. It maps to CWE-288 and CWE-551. The supplied CVSS vector indicates confidentiality impact only. Whether returned content exposes usable secrets depends on application-specific rendering and downstream authorization controls.
Mitigation direction
Upgrade Next.js 15.x deployments to 15.5.16 or later.
Upgrade Next.js 16.x deployments to 16.2.5 or later.
Confirm sensitive data has authorization enforcement independent of route-matching behavior.
Review the Next.js advisory and applicable Red Hat guidance before using temporary mitigations.
Validation and detection
Inventory deployed Next.js versions, including build artifacts and lockfiles.
Identify App Router applications using middleware or proxy rules for authorization.
Verify protected content remains inaccessible across framework-generated prefetch route variants.
Review access logs for unusual .rsc or segment-prefetch requests targeting protected pages.
Run authorization regression tests after upgrading.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-288: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.