fix(deps): bump next to 16.3.6 for GHSA-vcvr-r3jv-pc5j - #245
Merged
Merged
Conversation
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Deploying website with
|
| Latest commit: |
c92dc1c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://f12e8cd5.website-70y.pages.dev |
| Branch Preview URL: | https://claude-nextjs-security-relea.website-70y.pages.dev |
yigitdot
deleted the
claude/nextjs-security-release-sept-2026-05f564
branch
September 23, 2026 12:41
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.
Bumps
next16.3.4 → 16.3.6, the out-of-band patch Vercel shipped on 2026-09-22 for GHSA-vcvr-r3jv-pc5j.The advisory
Critical, CVSS v4 9.5 — RCE in the Node implementation of
ImageResponsefromnext/og, triggered when attacker-controlled values reach SVG content, attributes, or styles. Affected: 16.2.0 – 16.3.5. Fixed in 16.3.6 (and15.5.26on the 15 line). The Edge implementation is unaffected.Why it applies to us
We do call the vulnerable code path.
app/blog/[slug]/opengraph-image.tsximportsImageResponsefromnext/og, and no route underapp/setsexport const runtime = "edge"— so it is the affected Node implementation, not the unaffected Edge one.Runtime exposure is nil: under
output: "export"the card renders at build time only and there is no server. The interpolated values (post.title,dottedDate(post.date),seriesLabel(post.seriesNumber)) all come from our own committed MDX frontmatter.The one non-theoretical path is CI.
.github/workflows/website.ymlrunspnpm buildonpull_request, including from forks, so a fork PR adding a post with a crafted title would render attacker-supplied text through the vulnerable renderer on the runner. Blast radius is narrow — it ispull_request(notpull_request_target) withpermissions: contents: read, so no secrets are exposed and the runner is ephemeral — but it is reason enough not to sit on a 9.5.Scope
nextonly. The lockfile diff touchesnext,@next/env, the eight@next/swc-*binaries, and dropsnanoid@3.3.18(16.3.6 no longer depends on it). Nothing else moves.eslint-config-nextstays at 16.2.10 — dev-only, unrelated to this advisory, and left for the monthly Dependabotdev-dependenciesgroup rather than mixed into a security patch.Verification
Full CI sequence run locally, all green:
nextversion16.3.6pnpm lintpnpm format:checkpnpm typecheckpnpm testpnpm build+check:out+check:og-imageout/Since
next/ogis the package that changed, the 8 regenerated blog cards were also checked by hand — all 1200×630, and the longest title (Stablecoin Settlement Is Not a Footnote) still renders its eyebrow, two-line 60px auto-shrunk title, and the date · §05 · whisper-dot row inside the canvas. No layout shift from the Satori bump.🤖 Generated with Claude Code