Skip to content

fix(deps): patch six Next.js advisories with next 16.3.8 - #389

Merged
AdamXweb merged 1 commit into
mainfrom
fix/next-16-3-8-advisories
Oct 8, 2026
Merged

AdamXweb merged 1 commit into
mainfrom
fix/next-16-3-8-advisories

Conversation

@adamXbot

@adamXbot adamXbot commented Oct 8, 2026

Copy link
Copy Markdown
Collaborator

CI's required quality check fails on every branch at "Audit production dependency tree": pnpm audit --prod reports six new Next.js advisories, all fixed in 16.3.8.

Advisory Severity Issue
GHSA-cjq9-62q9-8jv4 high Server-side request forgery in Image Optimization
GHSA-mcj8-r9mp-w47p moderate Cache poisoning in SSG/ISR rendering (cross-user content substitution)
GHSA-4jqv-mc3x-m676 moderate Cache poisoning of SSG and ISR pages in self-hosted apps
GHSA-f87g-xv8r-7p7x moderate Information disclosure in App Router metadata image routes
GHSA-3w37-wq28-93x7 moderate A pending use cache fill can leak Draft Mode content
GHSA-39w2-rjm5-chcv low Information disclosure in the development server's MCP endpoint

Next.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: next 16.3.6 → 16.3.8, still an exact pin.
  • pnpm-lock.yaml: only next, @next/env and the eight @next/swc-* binaries, plus the next-intl and @storybook/nextjs entries whose keys name next. 16.3.8 declares the same dependency ranges as 16.3.6 apart from its own @next/* packages. Both peers accept it (next-intl 4.13.4 and @storybook/nextjs 10.5.5 take ^16.0.0), and nothing else pins Next.js.
  • pnpm-workspace.yaml: the sharp override stays, because 16.3.8 still declares ^0.35.4. Its comment now says so.
  • CHANGELOG.md: a ### Security entry under [Unreleased].

/legal reads versions from package.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-lockfile passes.
  • pnpm lint checked 1038 files with no issues; pnpm typecheck and pnpm lint:i18n pass.
  • pnpm test: 1083 tests, 1079 pass, 0 fail, 4 skipped (the opt-in live App Store tests).
  • pnpm test:release: 30 pass.
  • pnpm build passes on Next.js 16.3.8. The CSP hash generator covered 38 static routes, so the static-routes guard held.
  • Playwright was not run locally; CI runs it.

Not fixed here

pnpm audit (dev included) still reports three Storybook-only findings. None is in the production tree, so CI's audit passes:

pnpm peers check still lists TypeScript 7 against @typescript-eslint's range, as before; it is unrelated to this bump.

🤖 Generated with Claude Code

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>
@adamXbot
adamXbot requested a review from AdamXweb as a code owner October 8, 2026 12:01
@AdamXweb
AdamXweb merged commit adf1a54 into main Oct 8, 2026
20 checks passed
@AdamXweb
AdamXweb deleted the fix/next-16-3-8-advisories branch October 8, 2026 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants