GitHub Advisoryadvisory · npm

GHSA-267c-6grr-h53f Next.js has a Middleware / Proxy bypass in App Router applications via segment-prefetch routes

HIGH Published 2026-05-11 Modified 2026-05-14 Official page ↗
Aliases
CVE-2026-44575
Ecosystem
npm
Packages
next
Severity
High
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Weaknesses
CWE-288
Reviewed
2026-05-11

Affected packages

• npm next: >= 15.2.0, < 15.5.16 → fixed in 15.5.16 • npm next: >= 16.0.0, < 16.2.5 → fixed in 16.2.5

Description

Impact 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. Fix We now include App Router transport variants when generating middleware matchers, so middleware protections are applied consistently to those requests as well as to the normal page URL. Workarounds If you cannot upgrade immediately, enforce authorization in the underlying route or page logic instead of relying solely on middleware.

Related

Alias · CVE (1)

  • CVE-2026-44575 Next.js is a React framework for building full-stack web applications. vulnerability

Weakness · CWE (1)

  • CWE-288 Authentication Bypass Using an Alternate Path or Channel weakness

References