Enforce nextjs peerDependency to 14.2.25 and 15.2.3 #1988
Merged
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.
📋 Changes
With this PR, I am proposing to update the peerDependencies to ensure users use a version of NextJS that isn't vulnerable to GHSA-f82v-jwr5-mffw.
Looking at the advisory, we can see the issue is fixed in nextjs 14.2.25 and 15.2.3
This would technically be a breaking change, but as this SDK relies on authorization in middleware, I think we should release this as a minor version bump.
A more in-depth write-up of the issue is available here.
If upgrading NextJS version to any non-vulnerable version is not possible in your application, ensure to add the recommended protection:
For more on why this code helps prevent the issue, read the in-depth write up.
📎 References
GHSA-f82v-jwr5-mffw
https://zeropath.com/blog/nextjs-middleware-cve-2025-29927-auth-bypass
🎯 Testing
N/A