This repository was archived by the owner on Jul 29, 2026. It is now read-only.
fix(security): upgrade Next.js 16.2.0 → 16.2.12 to patch high-severity CVEs - #97
Draft
caimanoliveira wants to merge 3 commits into
Draft
fix(security): upgrade Next.js 16.2.0 → 16.2.12 to patch high-severity CVEs#97caimanoliveira wants to merge 3 commits into
caimanoliveira wants to merge 3 commits into
Conversation
Addresses high-severity vulnerabilities including XSS via CSP nonces, cache poisoning, middleware/proxy bypass, SSRF, and DoS in Server Components, Image Optimization API, and Server Actions. Also fixes ws uninitialized memory disclosure (GHSA-58qx-3vcg-4xpx) via npm audit fix. Co-Authored-By: Claude <noreply@anthropic.com>
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
… versions Python 3.9 was removed from GitHub Actions runners; update to 3.12. Also update actions/checkout v2→v4 and actions/setup-python v1→v5 to resolve Node 20 deprecation warnings.
The file was previously committed but node_modules/ is listed in .gitignore. Remove it from the index so git stops tracking it.
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 subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.0to16.2.12to address high-severity vulnerabilitieswsuninitialized memory disclosure vianpm audit fixVulnerabilities Fixed
Next.js CVEs (GHSA):
GHSA-ffhc-5mcf-pf4q)GHSA-vfv6-92ff-j949)GHSA-267c-6grr-h53f,GHSA-26hh-7cqf-hhc6)GHSA-3g8h-86w9-wvmq)GHSA-q4gf-8mx6-v5v3,GHSA-8h8q-6873-q5fj)GHSA-89xv-2m56-2m9x) and rewrites (GHSA-p9j2-gv94-2wf4)ws:
GHSA-58qx-3vcg-4xpx)GHSA-96hv-2xvq-fx4p)Remaining Known Vulnerabilities
3 vulnerabilities in Next.js's bundled
postcssandsharpremain. The only npm-suggested fix is to downgrade tonext@9.3.3, which would be a catastrophic breaking change. These are tracked upstream in the Next.js project and cannot be addressed at the project level without waiting for a Next.js release that updates its internal dependencies.Commits in Last 24 Hours
None. Most recent project work was 2026-04-18 (P3 portal trilhas feature set, merged via PR #1).
Generated by Claude Code