chore(deps): bump next to 14.2.35 in docs (GHSA-f82v-jwr5-mffw)#13445
chore(deps): bump next to 14.2.35 in docs (GHSA-f82v-jwr5-mffw)#13445Bekacru wants to merge 1 commit into
Conversation
next@14.2.21 falls in the vulnerable range of the Next.js middleware authorization bypass advisory (fixed in 14.2.25). Bump to the latest 14.2.x patch, which also includes the subsequent 14.2.3x security fixes. The other resolved version in the workspace (15.3.1) is already outside the affected ranges.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
2 Skipped Deployments
|
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
|
Warning Review the following alerts detected in dependencies. According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.
|
☕️ Reasoning
GHSA-f82v-jwr5-mffw (Authorization Bypass in Next.js Middleware, critical) affects
next < 14.2.25on the 14.x line. The docs site pinsnext@14.2.21, which is in range.docstonext@14.2.35— the latest 14.2.x patch, which includes the middleware fix plus the later 14.2.3x security patches.nextin the workspace is 15.3.1 (packages/next-authdev dep andapps/dev/nextjs), already outside the affected ranges (fixed ≥ 15.2.3).apps/examples/*usenext: latestand are outside the pnpm workspace, so they resolve a current (safe) version at install time.Lockfile note: the diff includes peer-suffix rewrites for the new
nextversion and an incidental within-rangevite5.3.1 → 5.4.21 update from pnpm re-resolving peer-dependent subgraphs.🧢 Checklist
next buildpasses)