CVE-2026-44575: CWE-288: Authentication Bypass Using an Alternate Path or Channel in vercel next.js
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.
AI Analysis
Technical Summary
CVE-2026-44575 is an authentication bypass vulnerability in the Next.js React framework affecting App Router applications relying on middleware or proxy-based authorization checks. In affected versions (>=15.2.0 <15.5.16 and >=16.0.0 <16.2.5), specially crafted .rsc and segment-prefetch URLs can resolve to the same page without triggering the expected middleware authorization rules, allowing unauthorized access to protected content. The vulnerability is addressed in Next.js versions 15.5.16 and 16.2.5. The CVSS 3.1 score is 7.5 (High), reflecting network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact.
Potential Impact
This vulnerability allows attackers to bypass authorization checks in affected Next.js applications, potentially exposing protected content without proper authentication. The impact is limited to confidentiality as integrity and availability are not affected. Exploitation does not require privileges or user interaction and can be performed remotely over the network.
Mitigation Recommendations
A fix is available in Next.js versions 15.5.16 and 16.2.5. Users should upgrade affected versions to these fixed releases to remediate the vulnerability. There is no indication from the vendor advisory that alternative mitigations or temporary workarounds are available or recommended.
CVE-2026-44575: CWE-288: Authentication Bypass Using an Alternate Path or Channel in vercel next.js
Description
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.
CVSS v3.1
Score 7.5high
Affected software
pkg:github/vercel/next.jsRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-44575 is an authentication bypass vulnerability in the Next.js React framework affecting App Router applications relying on middleware or proxy-based authorization checks. In affected versions (>=15.2.0 <15.5.16 and >=16.0.0 <16.2.5), specially crafted .rsc and segment-prefetch URLs can resolve to the same page without triggering the expected middleware authorization rules, allowing unauthorized access to protected content. The vulnerability is addressed in Next.js versions 15.5.16 and 16.2.5. The CVSS 3.1 score is 7.5 (High), reflecting network attack vector, low complexity, no privileges required, no user interaction, and high confidentiality impact.
Potential Impact
This vulnerability allows attackers to bypass authorization checks in affected Next.js applications, potentially exposing protected content without proper authentication. The impact is limited to confidentiality as integrity and availability are not affected. Exploitation does not require privileges or user interaction and can be performed remotely over the network.
Mitigation Recommendations
A fix is available in Next.js versions 15.5.16 and 16.2.5. Users should upgrade affected versions to these fixed releases to remediate the vulnerability. There is no indication from the vendor advisory that alternative mitigations or temporary workarounds are available or recommended.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-06T21:49:12.424Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-44575","vendor":"Red Hat"}]
Threat ID: 6a04af94cbff5d8610ed2999
Added to database: 05/13/2026, 17:06:28 UTC
Last enriched: 07/30/2026, 21:40:55 UTC
Last updated: 07/31/2026, 21:33:37 UTC
Views: 126
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.