Repository navigation
fix(deps): patch six Next.js advisories with next 16.3.8 - #389
Merged
Merged
Conversation
pnpm audit --prod, which CI's required quality check runs, now fails on six Next.js advisories, all fixed in 16.3.8: GHSA-cjq9-62q9-8jv4 (high, SSRF in Image Optimization), GHSA-mcj8-r9mp-w47p and GHSA-4jqv-mc3x-m676 (cache poisoning of SSG and ISR pages), GHSA-f87g-xv8r-7p7x (App Router metadata image routes), GHSA-3w37-wq28-93x7 (use cache leaking Draft Mode content) and GHSA-39w2-rjm5-chcv (low, the development server's MCP endpoint). Pin next 16.3.6 -> 16.3.8, exact as before. 16.3.8 declares the same ranges as 16.3.6 apart from its own @next/* packages, so the lockfile changes only next, @next/env and the eight @next/swc-* binaries, plus the next-intl and @storybook/nextjs keys that name next; both accept ^16 as a peer. The sharp override stays: 16.3.8 still declares ^0.35.4, and its comment now says so. Next.js's server runs only in the Docker image's Node rollback and in development; the default Rust image and the desktop app serve a static build. /legal reads versions from package.json and needs no edit. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Oct 8, 2026
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.
CI's required
qualitycheck fails on every branch at "Audit production dependency tree":pnpm audit --prodreports six new Next.js advisories, all fixed in 16.3.8.use cachefill can leak Draft Mode contentNext.js's server runs only in the Docker image's Node rollback (
BACKEND=node) and in development; the default Rust image and the desktop app serve a static build.Change
package.json:next16.3.6 → 16.3.8, still an exact pin.pnpm-lock.yaml: onlynext,@next/envand the eight@next/swc-*binaries, plus thenext-intland@storybook/nextjsentries whose keys namenext. 16.3.8 declares the same dependency ranges as 16.3.6 apart from its own@next/*packages. Both peers accept it (next-intl4.13.4 and@storybook/nextjs10.5.5 take^16.0.0), and nothing else pins Next.js.pnpm-workspace.yaml: thesharpoverride stays, because 16.3.8 still declares^0.35.4. Its comment now says so.CHANGELOG.md: a### Securityentry under[Unreleased]./legalreads versions frompackage.json, so it needs no edit.Verification
pnpm audit --prod: before, 6 vulnerabilities (1 high, 4 moderate, 1 low), the six above; after, no known vulnerabilities.pnpm install --frozen-lockfilepasses.pnpm lintchecked 1038 files with no issues;pnpm typecheckandpnpm lint:i18npass.pnpm test: 1083 tests, 1079 pass, 0 fail, 4 skipped (the opt-in live App Store tests).pnpm test:release: 30 pass.pnpm buildpasses on Next.js 16.3.8. The CSP hash generator covered 38 static routes, so the static-routes guard held.Not fixed here
pnpm audit(dev included) still reports three Storybook-only findings. None is in the production tree, so CI's audit passes:elliptic(GHSA-848j-6mx2-7j84) andbraces(GHSA-vfj7-8cjw-p6xm), as described in fix(deps): patch sharp and postcss-selector-parser advisories #385.pbkdf23.1.6 (GHSA-477h-4r7f-fvrx, moderate), through@storybook/nextjs→node-polyfill-webpack-plugin→crypto-browserify. 3.1.7 fixes it, so a scoped override would work. It is left out to keep this PR to the Next.js bump.pnpm peers checkstill lists TypeScript 7 against@typescript-eslint's range, as before; it is unrelated to this bump.🤖 Generated with Claude Code