NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-44574: Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

highCVSS 3.1 8.1GHSA-492v-c6pp-mqqv

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.

Published May 11, 2026 · Updated May 14, 2026

Affected packages

next

Ecosystem
npm
Affected
>= 15.4.0, < 15.5.16
Fixed in
15.5.16
Check
npm ls next

next

Ecosystem
npm
Affected
>= 16.0.0, < 16.2.5
Fixed in
16.2.5
Check
npm ls next

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

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.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries