fix(deps): bump next to 16.3.8 for GHSA-vcvr-r3jv-pc5j and GHSA-2xp9-vwfh-vxw4 - #16
Merged
Merged
Conversation
next 16.2.9 is inside the affected range of: - GHSA-vcvr-r3jv-pc5j: RCE in next/og ImageResponse (>=16.2.0 <16.3.6, patched 16.3.6) - GHSA-2xp9-vwfh-vxw4: unauthenticated RCE in the Image Optimization API with AVIF (<16.3.3) Bumps next and eslint-config-next to 16.3.8, the current npm latest. Dependency and lockfile change only. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FdeA8nzAPvx92LuUuozKM7
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
1 participant
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.
Why
Two critical Next.js advisories cover this repo's current version:
next/ogImageResponse. Affects>= 16.2.0, < 16.3.6. Patched in 16.3.6. Published 2026-09-30.>= 16.0.0, < 16.3.3.This PR moves to 16.3.8, the current npm
latest, which clears both floors.What changed
next16.2.9 to 16.3.8 andeslint-config-next16.2.9 to 16.3.8.package-lock.jsonupdated. Every lockfile change stays inside next's own dependency tree, all from registry.npmjs.org.Checks
These ran locally on Node 22.23.3 and npm 10.9.9, to match the CI matrix:
npm cinextversionnpm run typechecknpm run lintnpm testnpm run buildCI on this PR covers Node 20 and 22, plus the Docker build and boot smoke.
Generated with Claude Code (https://claude.com/claude-code)