Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-492v-c6pp-mqqv | Next.js has a Middleware / Proxy bypass through dynamic route parameter injection |
Thu, 14 May 2026 12:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:vercel:next.js:*:*:*:*:*:node.js:*:* |
Thu, 14 May 2026 11:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 13 May 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Vercel
Vercel next.js |
|
| Vendors & Products |
Vercel
Vercel next.js |
Wed, 13 May 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | Next.js: Middleware / Proxy bypass through dynamic route parameter injection | |
| Weaknesses | CWE-288 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-05-14T10:30:11.611Z
Reserved: 2026-05-06T21:49:12.424Z
Link: CVE-2026-44574
Updated: 2026-05-14T10:30:08.565Z
Status : Analyzed
Published: 2026-05-13T17:16:22.767
Modified: 2026-05-14T12:37:00.523
Link: CVE-2026-44574
No data.
OpenCVE Enrichment
Updated: 2026-05-13T18:30:46Z
Github GHSA