Advisory

GHSA-f82v-jwr5-mffw

Also known as: CVE-2025-29927

Summary

Authorization Bypass in Next.js Middleware

Details

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_)

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2025-03-21 15:20 UTC
Modified
2026-09-10 03:50 UTC

Affected packages and fixes

next

npm · All systems

Affected

  • introduced 13.0.0, fixed 13.5.9 (semver)

Fixed versions

13.5.9

Fix

next

npm · All systems

Affected

  • introduced 14.0.0, fixed 14.2.25 (semver)

Fixed versions

14.2.25

Fix

next

npm · All systems

Affected

  • introduced 15.0.0, fixed 15.2.3 (semver)

Fixed versions

15.2.3

Fix

next

npm · All systems

Affected

  • introduced 12.0.0, fixed 12.3.5 (semver)

Fixed versions

12.3.5

Fix

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences