Skip to content

Bump next to 15.5.28 and sharp to 0.35.5 (GHSA-2464-fhr4-w9xw) [SECURITY] - #88

Open
superbot-helper wants to merge 1 commit into
radcrew:mainfrom
superbot-helper:security/bump-next-15.5.28
Open

superbot-helper wants to merge 1 commit into
radcrew:mainfrom
superbot-helper:security/bump-next-15.5.28

Conversation

@superbot-helper

Copy link
Copy Markdown

Description

Bumps next from 15.5.18 to 15.5.28 in pnpm-lock.yaml, which closes GHSA-2464-fhr4-w9xw (critical, CVSS v4 9.5, CVE-2026-96889). The declared ^15.1.6 already admits the fix, so website/package.json is unchanged and only the lock moves.

The vulnerable code is sharp, not next. The advisory's workaround is "sharp >= 0.35.5", and the two upstream commits that fix it (5e3b687b, 9571ec89) change one line of source each — packages/next/package.json's optional dependency on sharp — plus their own lockfile. next 15.5.18 declares sharp: ^0.34.3, so this lock resolved sharp 0.34.5 — libvips 8.17.3, librsvg 2.61.2. Next 15.5.28 declares ^0.34.3 || ^0.35.5, which still admits 0.34.5, so bumping next alone would leave the old library installed. This patch moves both: next 15.5.28 and sharp 0.35.5 (libvips 8.18.7, librsvg 2.63.2). The other [email protected] in the tree belongs to @dynamic-labs/iconic and is untouched.

Per CVE-2026-96889, the flaw is a use-after-free in librsvg when an SVG contains nested XIncludes with duplicate entity declarations.

SECURITY.md asks for security reports by email rather than a public issue. This one is a dependency bump against an already-public advisory, so I put it here first; if you would rather take it through [email protected], say so and I will.

Component(s)

  • Website

Reach here: precautionary

I ran both arms with next start and requested the image optimizer:

  • /_next/image?url=/images/pets/tidefang.png&w=64&q=75 → 200, and an instrumented sharp was loaded and called from next/dist/server/image-optimizer.js. The optimizer → libvips path is live.
  • /_next/image?url=/icon.svg&w=64&q=75 → 400, "url" parameter is valid but image type is not allowed, logged as dangerouslyAllowSVG is disabled.

website/next.config.ts sets no dangerouslyAllowSVG, remotePatterns is empty, and the site's only SVG is its own fixed icon.svg. So I could not demonstrate the advisory's SVG trigger against this app: the fix is precautionary here, and only becomes load-bearing if someone enables SVG optimization or adds a route that serves SVG.

How Has This Been Tested?

  • pnpm install --frozen-lockfile exit 0 on both arms (pnpm 9.15.9).
  • pnpm build in website/ exit 0 on both arms.
  • 35 moved lock entries checked against the registry: all 35 integrities match, 13 MATCH / 22 ABSENT-BUT-NONE, 0 stale.
  • The lock diff touches only next, @next/*, sharp and @img/*; no other package version moves.

Not run: a proof-of-concept for CVE-2026-96889 (none is public), pnpm lint, pnpm test, and any deploy.

@vercel

vercel Bot commented Nov 2, 2026

Copy link
Copy Markdown

Someone is attempting to deploy a commit to the heyradcode's projects Team on Vercel.

A member of the Team first needs to authorize it.

@vercel
vercel Bot temporarily deployed to Preview – do-not-stop-backend November 2, 2026 00:41 Inactive
@vercel
vercel Bot temporarily deployed to Preview – do-not-stop-mobile November 2, 2026 00:41 Inactive
@vercel

vercel Bot commented Nov 2, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

2 Skipped Deployments
Project Deployment Actions Updated
do-not-stop-backend Skipped Skipped Nov 2, 2026 12:41am UTC
do-not-stop-mobile Skipped Skipped Nov 2, 2026 12:41am UTC

This branch was previously deployed

2 inactive deployments
Preview – do-not-stop-backend — fdbea1e1 Deployed Nov 2, 2026 by vercel[bot]
Preview – do-not-stop-mobile — fdbea1e1 Deployed Nov 2, 2026 by vercel[bot]
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