Next.js is a React framework for building full-stack web applications. From 15.4.0 to before 15.5.16 and 16.2.5, applications that rely on middleware to protect dynamic routes can be vulnerable to authorization bypass. In affected deployments, specially crafted query parameters can alter the dynamic route value seen by the page while leaving the visible path unchanged, which can allow protected content to be rendered without passing the expected middleware 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 show protected dynamic-route content to a user who should not receive it. A crafted request can make the page resolve a different route value than middleware evaluated, undermining middleware-based authorization while the visible path remains unchanged.
Executive priority
Prioritize rapid remediation for internet-facing applications handling sensitive or changeable data through middleware-protected dynamic routes. The high confidentiality and integrity impact warrants urgent inventory and upgrade work, although the supplied evidence does not establish active exploitation.
Technical view
CVE-2026-44574 is a network-reachable authorization bypass affecting Next.js 15.4.0 through 15.5.15 and 16.0.0 through 16.2.4. Query parameters can alter the dynamic route value presented to a page without changing the visible path or triggering the expected middleware decision. CVSS 3.1 is 8.1, with low attack complexity and low privileges required.
Likely exposure
Exposure is limited to affected Next.js versions where middleware or proxy logic protects dynamic routes. Applications using independent authorization checks within pages, route handlers, or data-access layers may have reduced exposure, but that protection is not established by the supplied sources.
Exploitation context
The supplied record is not in CISA KEV, and no provided source establishes active exploitation. The vulnerability is remotely reachable, requires low privileges according to the CVSS vector, needs no user interaction, and could compromise confidentiality and integrity in susceptible applications.
Researcher notes
The issue maps to CWE-288 and CWE-551. Its security boundary mismatch is between middleware evaluation and the dynamic route value consumed by the page. The supplied evidence does not quantify affected configurations, observed attacks, or whether compensating authorization controls fully prevent impact.
Mitigation direction
Upgrade Next.js 15.x deployments to version 15.5.16 or later.
Upgrade Next.js 16.x deployments to version 16.2.5 or later.
Add authorization checks at protected page, route-handler, or data-access boundaries.
Review Vercel and downstream vendor guidance for deployment-specific remediation.
Validation and detection
Inventory deployed Next.js versions, including lockfiles, build artifacts, and running images.
Identify dynamic routes whose authorization depends primarily on middleware or proxy logic.
Confirm protected pages independently validate the authenticated user's authorization.
Run authorized regression tests covering query parameters, dynamic route resolution, and middleware enforcement.
Verify production artifacts contain a fixed Next.js version after deployment.
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.
The CVE wording references privilege impact, so privilege escalation and authorization behavior review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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.
2CVSS vectors
5Timeline events
2ADP providers
9Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
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.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-288 · source CWE mapping
Authentication Bypass Using an Alternate Path or Channel
Authentication Bypass Using an Alternate Path or Channel represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization
Incorrect Behavior Order: Authorization Before Parsing and Canonicalization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.