CVE-2026-44573: CWE-863: Incorrect Authorization in vercel next.js
Next.js versions from 12.2.0 up to but not including 15.5.16, and from 16.0.0 up to but not including 16.2.5, have an authorization bypass vulnerability when using the Pages Router with i18n configured alongside middleware or proxy-based authorization. The middleware does not execute for locale-less data requests, allowing unauthorized access to server-side rendered JSON data for protected pages. This issue is fixed in versions 15.5.16 and 16.2.5.
AI Analysis
Technical Summary
CVE-2026-44573 is an incorrect authorization vulnerability (CWE-863) in the Next.js React framework affecting versions >=12.2.0 <15.5.16 and >=16.0.0 <16.2.5. When applications use the Pages Router with internationalization (i18n) configured and rely on middleware or proxy-based authorization, the middleware does not run for unprefixed locale-less data routes (/_next/data/<buildId>/<page>.json). This allows attackers to bypass authorization checks and retrieve server-side rendered JSON data for protected pages without proper authentication. The vulnerability is addressed in Next.js versions 15.5.16 and 16.2.5. The CVSS 3.1 base score is 7.5 (High), reflecting network attack vector, low complexity, no privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.
Potential Impact
Unauthorized users can access server-side rendered JSON data for protected pages in affected Next.js applications configured with i18n and middleware/proxy authorization. This leads to a confidentiality breach of potentially sensitive page data without requiring authentication or user interaction. There is no impact on integrity or availability.
Mitigation Recommendations
Upgrade Next.js to version 15.5.16 or later in the 15.x branch, or 16.2.5 or later in the 16.x branch to apply the official fix. Patch status is confirmed fixed in these versions. Until upgrading, avoid configurations that combine Pages Router with i18n and middleware/proxy authorization that rely on locale-less data routes, or implement additional authorization checks on these data endpoints.
CVE-2026-44573: CWE-863: Incorrect Authorization in vercel next.js
Description
Next.js versions from 12.2.0 up to but not including 15.5.16, and from 16.0.0 up to but not including 16.2.5, have an authorization bypass vulnerability when using the Pages Router with i18n configured alongside middleware or proxy-based authorization. The middleware does not execute for locale-less data requests, allowing unauthorized access to server-side rendered JSON data for protected pages. This issue is fixed in versions 15.5.16 and 16.2.5.
CVSS v3.1
Score 7.5high
Affected software
pkg:github/vercel/next.jsRun on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-44573 is an incorrect authorization vulnerability (CWE-863) in the Next.js React framework affecting versions >=12.2.0 <15.5.16 and >=16.0.0 <16.2.5. When applications use the Pages Router with internationalization (i18n) configured and rely on middleware or proxy-based authorization, the middleware does not run for unprefixed locale-less data routes (/_next/data/<buildId>/<page>.json). This allows attackers to bypass authorization checks and retrieve server-side rendered JSON data for protected pages without proper authentication. The vulnerability is addressed in Next.js versions 15.5.16 and 16.2.5. The CVSS 3.1 base score is 7.5 (High), reflecting network attack vector, low complexity, no privileges required, no user interaction, unchanged scope, high confidentiality impact, and no integrity or availability impact.
Potential Impact
Unauthorized users can access server-side rendered JSON data for protected pages in affected Next.js applications configured with i18n and middleware/proxy authorization. This leads to a confidentiality breach of potentially sensitive page data without requiring authentication or user interaction. There is no impact on integrity or availability.
Mitigation Recommendations
Upgrade Next.js to version 15.5.16 or later in the 15.x branch, or 16.2.5 or later in the 16.x branch to apply the official fix. Patch status is confirmed fixed in these versions. Until upgrading, avoid configurations that combine Pages Router with i18n and middleware/proxy authorization that rely on locale-less data routes, or implement additional authorization checks on these data endpoints.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-06T21:49:12.424Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
- Vendor Advisory Urls
- [{"url":"https://access.redhat.com/security/cve/CVE-2026-44573","vendor":"Red Hat"}]
Threat ID: 6a04af94cbff5d8610ed2993
Added to database: 05/13/2026, 17:06:28 UTC
Last enriched: 07/22/2026, 23:05:44 UTC
Last updated: 07/31/2026, 19:22:59 UTC
Views: 205
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.