CVE-2025-29927
Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Does this matter?
EPSS puts the probability of exploitation in the next 30 days at 99.2%, higher than 100% of all known CVEs. Patch or mitigate before the next change window.
Description
Next.js is a React framework for building full-stack web applications. Starting in version 1.11.4 and prior to versions 12.3.5, 13.5.9, 14.2.25, and 15.2.3, it is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. If patching to a safe version is infeasible, it is recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application. This vulnerability is fixed in 12.3.5, 13.5.9, 14.2.25, and 15.2.3.
- CVSS 3.1
- 9.1 CRITICALCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
- EPSS
- 99.22% probability · 100th percentile
- CISA KEV
- Not listed
- Weakness
- CWE-285, CWE-863
- Affected
- vercel/next.js
- Source
- security-advisories@github.com
References
- https://github.com/vercel/next.js/commit/52a078da3884efe6501613c7834a3d02a91676d2Patch
- https://github.com/vercel/next.js/commit/5fd3ae8f8542677c6294f32d18022731eab6fe48Patch
- https://github.com/vercel/next.js/releases/tag/v12.3.5Release Notes
- https://github.com/vercel/next.js/releases/tag/v13.5.9Release Notes
- https://github.com/vercel/next.js/security/advisories/GHSA-f82v-jwr5-mffwVendor Advisory
- http://www.openwall.com/lists/oss-security/2025/03/23/3Mailing List, Third Party Advisory
- http://www.openwall.com/lists/oss-security/2025/03/23/4Mailing List
- https://security.netapp.com/advisory/ntap-20250328-0002/Third Party Advisory
Source: NVD record, EPSS from FIRST.org, KEV from CISA. Refreshed daily.