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

Affected: vercel next.js, Red Hat Streams for Apache Kafka 2.9.4, Red Hat Trusted Artifact Signer 1.3, Red Hat Trusted Artifact Signer 1.4, Red Hat Enterprise Linux 10, Red Hat Enterprise Linux 7, Red Hat Enterprise Linux 8, Red Hat Enterprise Linux 9, Red Hat Enterprise Linux AI (RHEL AI) 3, Red Hat streams for Apache Kafka 3

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.

GHSA-492v-c6pp-mqqv — Next.js has a Middleware / Proxy bypass through dynamic route parameter injection

Affected: npm: next

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

Most recent entries from all

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

GHSA-492v-c6pp-mqqv — Next.js has a Middleware / Proxy bypass through dynamic route parameter injection