VDB
Sign up
HIGH8.1

GHSA-492v-c6pp-mqqv

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

Quick fix

GHSA-492v-c6pp-mqqv — next: upgrade to the fixed version with the command below.

npm install next@15.5.16

Details

### 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.

Are you affected?

Enter the version of the package you're using.

Affected packages

npm/next
Introduced in: 15.4.0Fixed in: 15.5.16
Fixnpm install next@15.5.16
npm/next
Introduced in: 16.0.0Fixed in: 16.2.5
Fixnpm install next@16.2.5

References