fix(security): upgrade Next.js 16.2.0→16.2.10 and patch ws vulnerabilities#82
Draft
caimanoliveira wants to merge 2 commits into
Draft
fix(security): upgrade Next.js 16.2.0→16.2.10 and patch ws vulnerabilities#82caimanoliveira wants to merge 2 commits into
caimanoliveira wants to merge 2 commits into
Conversation
Fixes 14 CVEs in next@16.2.0 (DoS via Server Components, Middleware/Proxy bypasses, cache poisoning, XSS, SSRF) by upgrading to 16.2.10. Also patches ws WebSocket memory disclosure/exhaustion via npm audit fix. Build verified clean on Next.js 16.2.10. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N2BsxcdUr6YHb8Qwk137NJ
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
…versions Python 3.9 is no longer available on ubuntu-latest runners (available: 3.10–3.14). Also bumps actions/checkout v2→v4 and actions/setup-python v1→v5 to avoid Node 20 deprecation warnings. Fixes the push trigger branch master→main. Co-Authored-By: Claude <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01N2BsxcdUr6YHb8Qwk137NJ
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
nextfrom16.2.0to^16.2.10, resolving 14 CVEs (high/moderate severity)wsWebSocket memory vulnerabilities vianpm audit fixCVEs Fixed in Next.js 16.2.10
beforeInteractivescriptsRemaining Known Issue
One
postcss <8.5.10(moderate XSS) lives inside Next.js's own bundled PostCSS. The only npm-suggested fix is downgrading tonext@9.3.3(breaking change) — that is not viable. This will resolve when the Next.js team ships an internal PostCSS bump.Test plan
next buildcompletes without errors on Next.js 16.2.10npm auditshows 0 high-severity vulnerabilities in direct dependencies🤖 Generated with Claude Code
https://claude.ai/code/session_01N2BsxcdUr6YHb8Qwk137NJ
Generated by Claude Code