Skip to content

fix(deps): upgrade Next.js to fix CVE-2026-94545 - #360

Merged
zjy365 merged 1 commit into
mainfrom
codex/fix-cve-2026-94545
Oct 13, 2026
Merged

zjy365 merged 1 commit into
mainfrom
codex/fix-cve-2026-94545

Conversation

@zjy365

@zjy365 zjy365 commented Oct 13, 2026

Copy link
Copy Markdown
Collaborator

Both Next.js applications pin 16.2.6, which is in the affected range for CVE-2026-94545. Upgrade next in the product UI and component registry to the patched 16.3.6 release, align @next/third-parties, and regenerate bun.lock with the required transitive dependencies. The current applications have no next/og or ImageResponse routes; this removes the vulnerable dependency version.

Reference: Next.js security advisory GHSA-vcvr-r3jv-pc5j.

Validation:

  • Bun 1.3.5: bun install --frozen-lockfile passes.
  • bun typecheck, bun check, and bun lint pass.
  • Production builds for apps/ui and apps/registry pass; both standalone outputs bundle Next.js 16.3.6.
  • A temporary benign regression probe inspects SVG passed by the bundled Node ImageResponse to the rasterizer, with sharp intercepted: a crafted SVG title injects a rectangle on 16.2.6 and is escaped on 16.3.6. No native exploit payload was executed.

@zjy365
zjy365 merged commit 9bcaa3c into main Oct 13, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant