Skip to content

fix(core): raise image-size and sharp floors past known advisories - #10

Open
BleedingDev wants to merge 1 commit into
rstackjs:mainfrom
BleedingDev:fix/image-size-sharp-security-floors
Open

BleedingDev wants to merge 1 commit into
rstackjs:mainfrom
BleedingDev:fix/image-size-sharp-security-floors

Conversation

@BleedingDev

@BleedingDev BleedingDev commented Sep 25, 2026 •

Copy link
Copy Markdown

image-size ICNS advisory | image-size JXL/HEIF advisory | sharp libvips advisory | sharp libheif advisory

Why the change

The published image-size and sharp ranges allow versions with known advisories, so raising their floors excludes those releases.

Special things to note

  • image-size requires Node 18 or newer; sharp remains an optional peer, so its floor affects projects that install it.
  • Local validation passes all 11 unit suites with 105 tests and 13 existing skips, core/react CJS/ESM and declaration builds, and all 88 Biome checks.
  • Current-head upstream test workflows require approval and have not run.

Change outline

 dependencies
-  image-size: ^2.0.1
+  image-size: ^2.0.4

 optional peerDependencies
-  sharp: >=0.33.5
+  sharp: >=0.35.4

- dependencies.image-size: ^2.0.1 -> ^2.0.4. image-size <= 2.0.2 has
  unbounded parser loops on malformed ICNS/JXL/HEIF input
  (GHSA-w3rx-r6r6-pgpr / CVE-2025-71330, GHSA-5p2g-fcmc-qvqq /
  CVE-2025-71329), fixed in 2.0.3.
- peerDependencies.sharp: >=0.33.5 -> >=0.35.4. sharp < 0.35.4 bundles
  vulnerable libvips/libheif (GHSA-f88m-g3jw-g9cj, GHSA-rgj7-g3m4-5g8c).

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>

This branch has not been deployed

No deployments
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