CVE-2026-44573: high-severity vulnerability in vercel next.js
Next.js: Middleware / Proxy bypass in Pages Router applications using i18n
Published · Updated
E-mail alert when it lands in KEV, gets a public PoC or its score goes up.
21Vexday Risk Score
No sign of exploitation. No public exploitation artifact known so far.
ssvc Trackcvss 7.5epss 0.8%
Next.js is a React framework for building full-stack web applications. From 12.2.0 to before 15.5.16 and 16.2.5, Applications using the Pages Router with i18n configured and middleware/proxy-based authorization can allow unauthorized access to protected page data through locale-less /_next/data/<buildId>/<page>.json requests. In affected configurations, middleware does not run for the unprefixed data route, allowing an attacker to retrieve SSR JSON for protected pages without passing the intended authorization checks. This vulnerability is fixed in 15.5.16 and 16.2.5.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Affected products
vercel · next.jsRelated CVEs — vercel next.js
In the same product, most dangerous first.
CVE-2025-29927CRITICALAuthorization Bypass in Next.js MiddlewareEPSS 99.2%CVE-2024-46982HIGHCache Poisoning in next.jsEPSS 61.0%CVE-2021-43803HIGHUnexpected server crash in Next.jsEPSS 47.3%CVE-2026-44578HIGHNext.js: Server-side request forgery in applications using WebSocket upgradesEPSS 35.5%CVE-2024-34351HIGHNext.js Server-Side Request Forgery in Server ActionsEPSS 5.5%CVE-2024-51479HIGHAuthorization bypass in Next.jsEPSS 4.0%
References
https://access.redhat.com/errata/RHSA-2026:34608https://access.redhat.com/errata/RHSA-2026:37272https://access.redhat.com/errata/RHSA-2026:40974https://access.redhat.com/errata/RHSA-2026:54435https://access.redhat.com/security/cve/CVE-2026-44573https://bugzilla.redhat.com/show_bug.cgi?id=2477199https://github.com/vercel/next.js/security/advisories/GHSA-36qx-fr4f-26g5https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44573.json