GHSA-492v-c6pp-mqqv CVE-2026-44574

Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

High npm

Severity: 8.1 / 10; High · CVSS 3.1
Exploit chance (EPSS): 0.64%; Chance of exploitation in the next 30 days. Higher than 50.51% of scored vulnerabilities.
Known exploited: No; Not in CISA's catalog
Weakness: CWE-288 Authentication Bypass Using an Alternate Path or Channel
Fix: 15.5.16; Upgrade next to this version or later

Description

Impact

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.

Fix

We now only honor internal route-parameter normalization in trusted routing flows and ignore externally supplied parameter encodings that should never have been accepted from ordinary requests.

Workarounds

If you cannot upgrade immediately, enforce authorization in route or page logic instead of relying solely on middleware path matching.

Affected versions

npm

Package	Vulnerable	Fixed in
next	`>= 15.4.0, < 15.5.16`	`15.5.16`
next	`>= 16.0.0, < 16.2.5`	`16.2.5`

How to fix

Move to the fixed version or later with your package manager, update the lockfile, and run your tests. If the package only arrives through another dependency, upgrade that dependency first. If none of its releases pulls a fixed version yet, force the version with your package manager's override.

next npm → `15.5.16`

npm

npm install next@15.5.16

yarn

yarn add next@15.5.16

pnpm

pnpm add next@15.5.16

Severity breakdown

CVSS 3.1 8.1

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

Attack vector: Network
Attack complexity: Low
Privileges required: Low
User interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: None

Weakness

CWE-288: Authentication Bypass Using an Alternate Path or Channel

The product requires authentication, but the product has an alternate path or channel that does not require authentication.

How to prevent it

Architecture and Design: Funnel all access through a single choke point to simplify how users can access a resource. For every access, perform a check to determine if the user has permissions to access the resource.

References

Advisories

nvd.nist.gov/vuln/detail/CVE-2026-44574

Packages

github.com/vercel/next.js

Timeline

May 11, 2026 Published
Oct 26, 2026 Last updated by the source
Oct 31, 2026 Latest EPSS score

Advisory	Severity	Why it's related
GHSA-673q-mjm6-r5xr Next.js: Unauthenticated Remote Code Execution in `use cache` functions returning typed arrays	Critical	Also affects next
GHSA-2464-fhr4-w9xw Next.js: Unauthenticated Remote Code Execution in Image Optimization API when SVG files are used	Critical	Also affects next
GHSA-p3m5-59mp-jv5r Next.js: Denial of Service in App Router using Server Actions	High	Also affects next
GHSA-3w37-wq28-93x7 Next.js: Pending `use cache` fill can leak Draft Mode content into regular responses and persisted pages	Medium	Also affects next
GHSA-4jqv-mc3x-m676 Next.js has cache poisoning of SSG and ISR pages in self-hosted applications	Medium	Also affects next
GHSA-39w2-rjm5-chcv Next.js has information disclosure in development server's Model Context Protocol endpoint	Medium	Also affects next
GHSA-f87g-xv8r-7p7x Next.js has information disclosure in App Router metadata image routes via dynamicParams bypass	Medium	Also affects next
GHSA-mcj8-r9mp-w47p Next.js has cache poisoning in SSG/ISR rendering that leads to cross-user content substitution and persistent denial of service	Medium	Also affects next

Is this in your code?

MergeHarbor checks every repository's dependencies against this database, ranks what matters by exploitability and reachability, routes it to the owning team and opens the fix pull request.

Check your repos with MergeHarbor