CVE-2026-44574
Vercel Next.js authentication bypass
- Published13 May 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
- https://access.redhat.com/errata/RHSA-2026:34608
- https://access.redhat.com/errata/RHSA-2026:37272
- https://access.redhat.com/errata/RHSA-2026:40974
- https://access.redhat.com/errata/RHSA-2026:54435
- https://access.redhat.com/security/cve/CVE-2026-44574
- https://bugzilla.redhat.com/show_bug.cgi?id=2477207
- https://github.com/vercel/next.js/security/advisories/GHSA-492v-c6pp-mqqv
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44574.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-44574 being actively exploited?
CVE-2026-44574 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.67%.
How severe is CVE-2026-44574?
CVE-2026-44574 has a CVSS 3.1 base score of 8.1, rated high. EPSS estimates a 0.67% probability of exploitation.
Which products are affected by CVE-2026-44574?
Affected products include Vercel Next.js.
How do I fix CVE-2026-44574?
Upgrade affected software to a fixed version, for example Vercel Next.js 15.5.16 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-44574 against the real software inventory on every managed device, as each hourly inventory arrives. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.