Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
📦 npm

GHSA-f82v-jwr5-mffw

CRITICAL

Authorization Bypass in Next.js Middleware

Also known asCVE-2025-29927
Published
Mar 21, 2025
Updated
Mar 4, 2026
Affected
4 pkgs
Patched
4 / 4
Exploits
24 known

EPSS Exploitation Probability

via FIRST.org ↗
92.1%probability of exploitation in next 30 days
Very High Risk100th percentile0.00%
91.1%91.9%92.7%93.5%91.6%92.1%Dec 25Apr 26Jun 26

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

4 pkgs affected
📦next📦next📦next📦next

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects npm packages — download data is not available via public APIs for these ecosystems.

Description

Impact

It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.

Patches

  • For Next.js 15.x, this issue is fixed in 15.2.3
  • For Next.js 14.x, this issue is fixed in 14.2.25
  • For Next.js 13.x, this issue is fixed in 13.5.9
  • For Next.js 12.x, this issue is fixed in 12.3.5
  • For Next.js 11.x, consult the below workaround.

Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability.

Workaround

If patching to a safe version is infeasible, we recommend that you prevent external user requests which contain the x-middleware-subrequest header from reaching your Next.js application.

Credits

  • Allam Rachid (zhero;)
  • Allam Yasser (inzo_)

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
📦npmnext13.0.0&&< 13.5.913.5.9
📦npmnext14.0.0&&< 14.2.2514.2.25
📦npmnext15.0.0&&< 15.2.315.2.3
📦npmnext12.0.0&&< 12.3.512.3.5
Exploits & PoCs
24

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

EDB-52124webappsmultiple

Next.js Middleware 15.2.2 - Authorization Bypass

by kOaDT · Apr 5, 2025

Frequently Asked Questions

# Impact It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware. # Patches * For Next.js 15.x, this issue is fixed in `15.2.3` * For Next.js 14.x, this issue is fixed in `14.2.25` * For Next.js 13.x, this issue is fixed in 13.5.9 * For Next.js 12.x, this issue is fixed in 12.3.5 * For Next.js 11.x, consult the below workaround. _Note: Next.js deployments hosted on Vercel are automatically protected against this vulnerability._ # Workaround If patching to a safe version is infeasible, we recommend that you prevent external
O3 Security · Impact-Aware SCA

Is GHSA-f82v-jwr5-mffw in your stack?

O3 detects GHSA-f82v-jwr5-mffw across npm dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.