sharp : Vulnerability in librsvg dependency CVE-2026-96889
Published 6 Oct 2026 · Updated 21 Oct 2026
Affected package
- Affected
- <0.35.5
- Fixed in
- 0.35.5
npm install sharp@0.35.5Details
Impact
A memory-related vulnerability has been discovered and fixed in the upstream librsvg dependency. When certain runtime-specific conditions apply, this vulnerability can lead to possible remote code execution (RCE) on glibc-based Linux.
Patches
Using prebuilt binaries provided by sharp?
Most people rely on the prebuilt binaries provided by sharp.
Please upgrade sharp to the latest version, currently 0.35.5, which provides librsvg 2.63.2.
Using a globally-installed librsvg?
Please ensure you are using the latest librsvg 2.63.2.
Workarounds
Add the following to your code to prevent sharp from decoding SVG images.
sharp.block({ operation: ["VipsForeignLoadSvg"] });To avoid RCE, ensure you are using a node executable binary compiled as a Position Independent Executable (PIE). Most Linux package managers already use this security-hardening feature however be warned that the "official" Node.js binaries do not.
1
Is GHSA-wq5f-xc86-pv6w in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected sharp, and gives you the command that fixes it.
References
- Linkgithub.com/lovell/sharp/security/advisories/GHSA-wq5f-xc86-pv6w
- Linkgithub.com/lovell/sharp/commit/96de105d9d36ab04c76c2b78b97255171630d236
- Packagegithub.com/lovell/sharp
- Linkgithub.com/lovell/sharp/releases/tag/v0.35.5
- Linkgitlab.gnome.org/GNOME/librsvg/-/work_items/1241
- Linkwww.cve.org/CVERecord?id=CVE-2026-96889
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.