Repository navigation
fix(deps): patch sharp to 0.35.5 - #1151
Conversation
Raise the existing sharp override to 0.35.5 for GHSA-wq5f-xc86-pv6w / CVE-2026-96889 (Dependabot alert #246): a memory-safety bug in the bundled librsvg, with possible remote code execution, fixed in sharp >=0.35.5. The selector ceiling moves with the pin so 0.35.4 cannot resolve. sharp is still reached only as an optional dependency of next. The lockfile change is limited to sharp and its @img/* platform binaries (@img/sharp-* 0.35.5, @img/sharp-libvips-* 1.3.4). 0.35.5 was published 2026-09-27, outside the 7-day minimumReleaseAge window.
|
Codex Review SummaryThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
freshtonic
left a comment
There was a problem hiding this comment.
Review of 7c653ec. I found no blocking defect.
What I checked
- Advisory. GHSA-wq5f-xc86-pv6w names
< 0.35.5, first patched0.35.5. The selector atpnpm-workspace.yaml:163('sharp@<0.35.5': '0.35.5') matches the advisory exactly. - Coverage. The PR lockfile has no
sharp@0.35.4and nolibvips1.3.3 entry. The only consumer snapshot issharp: 0.35.5. - Lockfile scope. The description says that you regenerated with
minimum-release-age=0. I compared the lockfile diff: every changed line is asharp,@img/sharp-*orlibvipsentry. No other package moved, so the cooldown bypass did not pull in a new version of anything else. - Changeset. Not needed.
sharpcomes in only as an optional dependency ofnext. pnpm overrides do not ship to consumers. - CI. 23 checks pass and 11 skip (path filters). No failures.
Overlap with #1197
#1197 has a text conflict with this PR in pnpm-lock.yaml. GitHub blocks that merge, so it is safe. But #1197 does not fix this advisory by itself: it keeps the old override sharp@<0.35.4: 0.35.4 (its pnpm-lock.yaml:46), and sharp stays at 0.35.4 even with next 15.5.27. Merge this PR first. Then let Dependabot recreate #1197. Do not resolve the conflict by hand in favour of #1197's lockfile.
Summary
Raises the existing
sharppnpm override inpnpm-workspace.yamlfrom 0.35.4 to 0.35.5 to fix GHSA-wq5f-xc86-pv6w / CVE-2026-96889 (Dependabot alert #246). The bundled librsvg has a memory-safety bug that may allow remote code execution. sharp is still reached only as an optional dependency ofnext(image optimization).'sharp@<0.35.4': '0.35.4'->'sharp@<0.35.5': '0.35.5'. The selector ceiling moves with the pin, as in the earlier sharp bumps.sharpand its@img/*platform binaries change (@img/sharp-*0.35.4 -> 0.35.5,@img/sharp-libvips-*1.3.3 -> 1.3.4). No other packages change.minimumReleaseAgewindow.Verification
pnpm install --frozen-lockfilesucceeds.pnpm why sharp -rreports a single version, sharp@0.35.5 (via next@15.5.24).pnpm-lock.yaml.require('sharp').versions: sharp 0.35.5, vips 8.18.7, rsvg 2.63.2).@img/*binaries match the npm registry.Note: the lockfile was regenerated with
--config.minimum-release-age=0for this run only. Without it, changing the override forces a full re-resolve, and the cooldown then downgrades two versions that are already on main (express-rate-limit 8.7.1 -> 8.7.0, acorn 8.19.0 -> 8.18.0). The repo'sminimumReleaseAgesetting is unchanged.Summary by CodeRabbit