You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
[!NOTE]
This release is backporting bug fixes. It does not include all pending features/changes on canary.
This release contains a security patch for CVE-2025-29927.
Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.
This PR includes no changesets
When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types
renovatebot
changed the title
fix(deps): update dependency next to v14.1.1 [security]
fix(deps): update dependency next to v14.1.1 [security] - autoclosed
Mar 19, 2025
renovatebot
changed the title
fix(deps): update dependency next to v14.1.1 [security] - autoclosed
fix(deps): update dependency next to v14.1.1 [security]
Mar 21, 2025
renovatebot
changed the title
fix(deps): update dependency next to v14.1.1 [security]
fix(deps): update dependency next to v15.2.3 [security]
Mar 21, 2025
renovatebot
changed the title
fix(deps): update dependency next to v15.2.3 [security]
fix(deps): update dependency next to v15.2.3 [security] - autoclosed
Mar 24, 2025
renovatebot
changed the title
fix(deps): update dependency next to v15.2.3 [security] - autoclosed
fix(deps): update dependency next to v15.2.3 [security]
Mar 27, 2025
renovatebot
changed the title
fix(deps): update dependency next to v15.2.3 [security]
fix(deps): update dependency next to v15.2.3 [security] - autoclosed
Mar 27, 2026
renovatebot
changed the title
fix(deps): update dependency next to v15.2.3 [security] - autoclosed
chore(deps): update dependency next to v15.2.3 [security]
Mar 30, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This PR contains the following updates:
15.2.1→15.2.3GitHub Vulnerability Alerts
CVE-2025-29927
Impact
It is possible to bypass authorization checks within a Next.js application, if the authorization check occurs in middleware.
Patches
15.2.314.2.25Note: 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-subrequestheader from reaching your Next.js application.Credits
Release Notes
vercel/next.js (next)
v15.2.3Compare Source
Core Changes
Credits
Huge thanks to @ijjk, @ztanner, and @huozhi for helping!
v15.2.2Compare Source
Core Changes
d55cc79b-20250228to443b7ff2-20250303: #76804443b7ff2-20250303toe03ac20f-20250305: #76842__next_app__module loading functions: #74566e03ac20f-20250305to029e8bd6-20250306: #76870xbutton present: #76898Example Changes
Misc Changes
redirectin client components: #76332labeler.json: #76828SyntaxContextfor__turbopack_esm__: #73544next.browserinstead ofwebdriverin pages/ client-navigation: #76867swc_coretov16.4.0: #76596v1.0.0-alpha.64: #76856__dirname: #76902Credits
Huge thanks to @pranathip, @gaojude, @ijjk, @eps1lon, @Nayeem-XTREME, @leerob, @styfle, @samcx, @sokra, @huozhi, @raunofreiberg, @mischnic, @lubieowoce, @unstubbable, @ztanner, @kdy1, @timneutkens, @wbinnssmith, @bgw, and @oscr for helping!
Configuration
📅 Schedule: Branch creation - "" (UTC), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Never, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR was generated by Mend Renovate. View the repository job log.