Skip to content

fix(deps): upgrade next to 15.5.24 — GHSA-2xp9-vwfh-vxw4 (Critical, unauth RCE in image optimizer) - #61

Open
ggcore0 wants to merge 1 commit into
masterfrom
security/next-avif-rce-ghsa-2xp9-vwfh-vxw4
Open

fix(deps): upgrade next to 15.5.24 — GHSA-2xp9-vwfh-vxw4 (Critical, unauth RCE in image optimizer)#61
ggcore0 wants to merge 1 commit into
masterfrom
security/next-avif-rce-ghsa-2xp9-vwfh-vxw4

Conversation

@ggcore0

@ggcore0 ggcore0 commented Aug 27, 2026

Copy link
Copy Markdown

Summary

Upgrades next to 15.5.24 to remediate GHSA-2xp9-vwfh-vxw4Unauthenticated Remote Code Execution in the Image Optimization API when AVIF files are used (Critical, CVSS v4 9.5).

A flaw in libheif, reached through the sharp image pipeline that Next.js uses for image optimization, allows arbitrary code execution when a crafted AVIF file is optimized. It needs no authentication and no user interaction. The patch disables AVIF optimization until the fix propagates through the dependency chain.

Affected next >= 10.0.0 < 15.5.24, next < 16.3.3
Patched 15.5.24 (15.x line), 16.3.3 (16.x line)
Upstream reference GHSA-g89c-p67h-r497 (libheif)

There are no backports below 15.5.24 — 14.x and older have no fixed release at all.

Why this repo

These are tutorial frontends that developers copy as a starting point, so the pinned versions propagate into downstream projects.

Changes

  • 08-Guess-Game/Frontend/package.json: next 15.0.215.5.24
  • 10-Advanced-Stake-Dapp/Frontend/package.json: next 15.0.215.5.24
  • 11-Bridge-Token-Using-Chainlink/frontend/package.json: next 15.2.415.5.24
  • 12-Core-MultiSig/Frontend/package.json: next 15.0.215.5.24
  • 13-Core-Test-Token-Faucet/Frontend/package.json: next 15.0.215.5.24
  • 14-Corelend/Frontend/package.json: next 15.0.215.5.24
  • 15-dns-protocol/Frontend/package.json: next 15.0.215.5.24
  • 16-Pump.Core/Frontend/package.json: next 15.0.215.5.24

Lockfiles regenerated with the repo's own package manager so this is ready to merge:

  • 08-Guess-Game/Frontend/package-lock.json
  • 10-Advanced-Stake-Dapp/Frontend/package-lock.json
  • 11-Bridge-Token-Using-Chainlink/frontend/package-lock.json
  • 12-Core-MultiSig/Frontend/package-lock.json
  • 13-Core-Test-Token-Faucet/Frontend/package-lock.json
  • 14-Corelend/Frontend/package-lock.json
  • 15-dns-protocol/Frontend/package-lock.json
  • 16-Pump.Core/Frontend/package-lock.json

The lockfile churn beyond next itself is confined to that dependency's own graph — @next/env, the @next/swc-* platform binaries, and sharp/@img/sharp-libvips-*. The libvips bump is worth noting: it carries the actual upstream libheif fix, not just the Next.js-side mitigation. No unrelated packages were upgraded.

Warning

This PR covers the eight tutorial frontends that are on the 15.x line. Other Next.js projects elsewhere in this repo may still need review.

Verification

  • next resolves to the patched version in every lockfile in this PR
  • Lockfile diff reviewed — no unrelated dependency upgrades
  • CI build/deploy green (over to reviewers)

🤖 Generated with Claude Code

https://claude.ai/code/session_016uwkrHFFWaqRawqPYg6733

Unauthenticated remote code execution in the Image Optimization API
when AVIF files are optimized, via libheif in the sharp pipeline
(Critical, CVSS v4 9.5).

Affected: next >=10.0.0 <15.5.24 and next <16.3.3.
Patched:  15.5.24 (15.x) and 16.3.3 (16.x). No backports exist below 15.5.24.

GHSA-2xp9-vwfh-vxw4

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016uwkrHFFWaqRawqPYg6733
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.

1 participant