Repository navigation
Conversation
Next.js 16.0.0 to 16.4.0 is affected by GHSA-2464-fhr4-w9xw (remote code execution in the image optimization API with SVG files), GHSA-673q-mjm6-r5xr (remote code execution in `use cache` functions returning typed arrays) and GHSA-p3m5-59mp-jv5r (denial of service through server actions). The site uses none of next/image, `use cache` or server actions, but /_next/image answers on the live site, so upgrade. eslint-config-next moves with it. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01NWyUpENgDRQLQtGTV6HpAD
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
This branch was successfully deployed
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
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.
What changed
nextandeslint-config-nextmove from 16.3.8 to 16.4.5. No content or code changes.Sources
Next.js 16.0.0 to 16.4.0 is affected by:
use cachefunctions returning typed arrays.The site uses none of
next/image,use cacheor server actions, so real exposure looks low. But/_next/imageresponds on the live site, so this upgrades anyway.After the upgrade,
npm audit --omit=devreports 0 vulnerabilities.npm run lint,npm run typecheck,npm test(17 tests) andnpm run buildall pass locally, and the build still prerenders every route.Checklist
status, the evidence meets the rules incontent/contribute.md. (No status changed.)last_verifiedon pages where I rechecked every claim. (None changed.)Generated by Claude Code