CVE-2026-44574
highpriority · track · 0OT risk · elevatedEPSS 0.006 · 50 %ileDEEURUUSEPSS · scored 2026-10-27
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.
cvss
Technical severity, 0–10. One row per scoring source.
base score 0–10 · higher = more severe · hover a vector to decode
ssvc
A stakeholder decision — act, attend, or track — from exploitation and impact.
weaknesses
The CWE weakness classes this flaw belongs to.
affected products (13)
Products and version ranges known to be affected.
advisories (2)
Vendor and ecosystem advisories describing this.
- WID-SEC-W-2026-1401Vercel Next.js: Mehrere SchwachstellenDeutsch2026-05-06csaf · cert_bundDE
Ein Angreifer kann mehrere Schwachstellen in Vercel Next.js ausnutzen, um Sicherheitsvorkehrungen zu umgehen, Cross-Site-Scripting-Angriffe durchzuführen, Daten zu manipulieren, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand zu verursachen.
- GHSA-492v-c6pp-mqqvNext.js has a Middleware / Proxy bypass through dynamic route parameter injection2026-05-11ghsa · osvUS
### 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.
also known as (5)
Other names and identifiers for this entity.
sources
Which sources assert this record, and when.
references (11)
External citations — patches, advisories, analysis.
- https://github.com/vercel/next.js/releasesPatchcnnvd
- https://nvd.nist.gov/vuln/detail/CVE-2026-44574cnnvd
- https://github.com/vercel/next.js/security/advisories/GHSA-492v-c6pp-mqqvenisa_euvd
- https://access.redhat.com/errata/RHSA-2026:34608nvd
- https://access.redhat.com/errata/RHSA-2026:37272nvd
- https://access.redhat.com/errata/RHSA-2026:40974nvd
- https://access.redhat.com/errata/RHSA-2026:54435nvd
- https://access.redhat.com/security/cve/CVE-2026-44574nvd
Attackers weaponise vulnerabilities like this against internet-exposed services. See what is exposed on your perimeter with a free passive scan.
Free scan