VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

sharp: vulnerability history, versions and safety

sharp is a package in the npm ecosystem. Vulert records 5 vulnerabilities for it across 119 releases, from Jun 2022 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
5 vulnerabilities recorded H4 M1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
3 in the last 12 months

Most recent disclosure 06 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all sharp vulnerabilities

Vulert verdict on sharp 0.35.5 i

Updated on 23 Oct 2026

Good news: 0.35.5, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 5.

Package health score 81/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 0.35.5 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.35.5 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.35.5 — unaffected i
  • Vulnerabilities on record 5 over 4 years · 3 in the last year i
  • Latest disclosure 06 Oct 2026 i
  • Highest CVSS 8.9 i
  • With no published fix 0 i
  • Depended on by 9,257 packages i
  • Stars 32,763 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for sharp, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.35.5 27 Sep 2026 none Apache-2.0 — Details →
0.35.5-rc.1 27 Sep 2026 H1 Apache-2.0 Yes Details →
0.35.5-rc.0 22 Sep 2026 H1 Apache-2.0 Yes Details →
0.35.4 26 Aug 2026 H1 Apache-2.0 Yes Details →
0.35.4-rc.0 25 Aug 2026 H2 Apache-2.0 Yes Details →
0.35.3 01 Jul 2026 H2 Apache-2.0 Yes Details →
0.35.3-rc.2 30 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.3-rc.1 27 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.2 19 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.2-rc.2 18 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.2-rc.1 18 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.2-rc.0 16 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.1 11 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.1-rc.1 11 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.1-rc.0 11 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.0 10 Jun 2026 H2 Apache-2.0 Yes Details →
0.35.0-rc.8 10 Jun 2026 H3 Apache-2.0 Yes Details →
0.35.0-rc.6 07 Jun 2026 H3 Apache-2.0 Yes Details →
0.35.0-rc.5 21 Apr 2026 H3 Apache-2.0 Yes Details →
0.35.0-rc.4 19 Apr 2026 H3 Apache-2.0 Yes Details →
0.35.0-rc.3 19 Apr 2026 H3 Apache-2.0 Yes Details →
0.35.0-rc.2 04 Apr 2026 H3 Apache-2.0 Yes Details →
0.35.0-rc.0 02 Jan 2026 H3 Apache-2.0 Yes Details →
0.34.5 06 Nov 2025 H3 Apache-2.0 Yes Details →
0.34.5-rc.1 06 Nov 2025 H3 Apache-2.0 Yes Details →
0.34.5-rc.0 05 Nov 2025 H3 Apache-2.0 Yes Details →
0.34.4 17 Sep 2025 H3 Apache-2.0 Yes Details →
0.34.4-rc.4 17 Sep 2025 H3 Apache-2.0 Yes Details →
0.34.4-rc.3 15 Sep 2025 H3 Apache-2.0 Yes Details →
0.34.3 10 Jul 2025 H3 Apache-2.0 Yes Details →
0.34.3-rc.1 09 Jul 2025 H3 Apache-2.0 Yes Details →
0.34.3-rc.0 14 Jun 2025 H3 Apache-2.0 Yes Details →
0.34.2 20 May 2025 H3 Apache-2.0 Yes Details →
0.34.2-rc.0 14 May 2025 H3 Apache-2.0 Yes Details →
0.34.1 07 Apr 2025 H3 Apache-2.0 Yes Details →
0.34.0 04 Apr 2025 H3 Apache-2.0 Yes Details →
0.34.0-rc.1 03 Apr 2025 H3 Apache-2.0 Yes Details →
0.34.0-rc.0 16 Mar 2025 H3 Apache-2.0 Yes Details →
0.33.5 16 Aug 2024 H3 Apache-2.0 Yes Details →
0.33.5-rc.1 14 Aug 2024 H3 Apache-2.0 Yes Details →
0.33.5-rc.0 13 Aug 2024 H3 Apache-2.0 Yes Details →
0.33.4 16 May 2024 H3 Apache-2.0 Yes Details →
0.33.4-rc.0 16 May 2024 H3 Apache-2.0 Yes Details →
0.33.3 23 Mar 2024 H3 Apache-2.0 Yes Details →
0.33.3-rc.0 22 Mar 2024 H3 Apache-2.0 Yes Details →
0.33.2 12 Jan 2024 H3 Apache-2.0 Yes Details →
0.33.2-rc.1 12 Jan 2024 H3 Apache-2.0 Yes Details →
0.33.2-rc.0 11 Jan 2024 H3 Apache-2.0 Yes Details →
0.33.1 17 Dec 2023 H3 Apache-2.0 Yes Details →
0.33.1-rc.3 17 Dec 2023 H3 Apache-2.0 Yes Details →
0.33.1-rc.2 17 Dec 2023 H3 Apache-2.0 Yes Details →
0.33.1-rc.0 12 Dec 2023 H3 Apache-2.0 Yes Details →
0.33.0 29 Nov 2023 H3 Apache-2.0 Yes Details →
0.33.0-rc.2 22 Nov 2023 H3 Apache-2.0 Yes Details →
0.33.0-alpha.11 10 Nov 2023 H3 Apache-2.0 Yes Details →
0.33.0-alpha.10 04 Nov 2023 H3 Apache-2.0 Yes Details →
0.33.0-alpha.9 13 Oct 2023 H3 Apache-2.0 Yes Details →
0.33.0-alpha.8 10 Oct 2023 H3 Apache-2.0 Yes Details →
0.33.0-alpha.7 10 Oct 2023 H3 Apache-2.0 Yes Details →
0.33.0-alpha.6 09 Oct 2023 H3 Apache-2.0 Yes Details →
0.33.0-alpha.4 06 Oct 2023 H3 Apache-2.0 Yes Details →
0.33.0-alpha.3 06 Oct 2023 H3 Apache-2.0 Yes Details →
0.32.6 18 Sep 2023 H3 Apache-2.0 Yes Details →
0.32.5 15 Aug 2023 H4 Apache-2.0 Yes Details →
0.32.4 21 Jul 2023 H4 Apache-2.0 Yes Details →
0.32.3 14 Jul 2023 H4 Apache-2.0 Yes Details →
0.32.2 11 Jul 2023 H4 Apache-2.0 Yes Details →
0.32.1 27 Apr 2023 H4 Apache-2.0 Yes Details →
0.32.0 24 Mar 2023 H4 Apache-2.0 Yes Details →
0.31.3 21 Dec 2022 H4 Apache-2.0 Yes Details →
0.31.2 04 Nov 2022 H4 Apache-2.0 Yes Details →
0.31.1 29 Sep 2022 H4 Apache-2.0 Yes Details →
0.31.0 05 Sep 2022 H4 Apache-2.0 Yes Details →
0.30.7 22 Jun 2022 H4 Apache-2.0 Yes Details →
0.30.6 30 May 2022 H4 Apache-2.0 Yes Details →
0.30.5 23 May 2022 H4 Apache-2.0 Yes Details →
0.30.4 18 Apr 2022 H4 M1 Apache-2.0 Yes Details →
0.30.3 14 Mar 2022 H4 M1 Apache-2.0 Yes Details →
0.30.2 02 Mar 2022 H4 M1 Apache-2.0 Yes Details →
0.30.1 09 Feb 2022 H4 M1 Apache-2.0 Yes Details →
0.30.0 01 Feb 2022 H4 M1 Apache-2.0 Yes Details →
0.29.3 14 Nov 2021 H4 M1 Apache-2.0 Yes Details →
0.29.2 21 Oct 2021 H4 M1 Apache-2.0 Yes Details →
0.29.1 07 Sep 2021 H4 M1 Apache-2.0 Yes Details →
0.29.0 17 Aug 2021 H4 M1 Apache-2.0 Yes Details →
0.28.3 24 May 2021 H4 M1 Apache-2.0 Yes Details →
0.28.2 10 May 2021 H4 M1 Apache-2.0 Yes Details →
0.28.1 05 Apr 2021 H4 M1 Apache-2.0 Yes Details →
0.28.0 29 Mar 2021 H4 M1 Apache-2.0 Yes Details →
0.27.2 22 Feb 2021 H4 M1 Apache-2.0 Yes Details →
0.27.1 27 Jan 2021 H4 M1 Apache-2.0 Yes Details →
0.27.0 22 Dec 2020 H4 M1 Apache-2.0 Yes Details →
0.26.3 16 Nov 2020 H4 M1 Apache-2.0 Yes Details →
0.26.2 14 Oct 2020 H4 M1 Apache-2.0 Yes Details →
0.26.1 20 Sep 2020 H4 M1 Apache-2.0 Yes Details →
0.26.0 25 Aug 2020 H4 M1 Apache-2.0 Yes Details →
0.25.4 12 Jun 2020 H4 M1 Apache-2.0 Yes Details →
0.25.3 17 May 2020 H4 M1 Apache-2.0 Yes Details →
0.25.2 20 Mar 2020 H4 M1 Apache-2.0 Yes Details →
0.25.1 07 Mar 2020 H4 M1 Apache-2.0 Yes Details →
0.25.0 07 Mar 2020 H4 M1 — Yes Details →
0.24.1 15 Feb 2020 H4 M1 — Yes Details →
0.24.0 16 Jan 2020 H4 M1 — Yes Details →
0.23.4 05 Dec 2019 H4 M1 — Yes Details →
0.23.3 17 Nov 2019 H4 M1 — Yes Details →
0.23.2 28 Oct 2019 H4 M1 — Yes Details →
0.23.1 26 Sep 2019 H4 M1 — Yes Details →
0.23.0 29 Jul 2019 H4 M1 — Yes Details →
0.22.1 25 Apr 2019 H4 M1 — Yes Details →
0.22.0 18 Mar 2019 H4 M1 — Yes Details →
0.21.3 19 Jan 2019 H4 M1 — Yes Details →
0.21.2 13 Jan 2019 H4 M1 — Yes Details →
0.21.1 07 Dec 2018 H4 M1 — Yes Details →
0.21.0 04 Oct 2018 H4 M1 — Yes Details →
0.20.8 05 Sep 2018 H4 M1 — Yes Details →
0.20.7 21 Aug 2018 H4 M1 — Yes Details →
0.20.6 20 Aug 2018 H4 M1 — Yes Details →
0.20.5 27 Jun 2018 H4 M1 — Yes Details →
0.20.4 20 Jun 2018 H4 M1 — Yes Details →
0.20.3 29 May 2018 H4 M1 — Yes Details →

The newest 120 of 194 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2022 1
  • 2023 1
  • 2026 3

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 3 of the 5 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for sharp

The 5 most severe of 5 vulnerabilities recorded for this package

Search all 5 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
Critical Remote Code Execution Vulnerability in Sharp Package Due to Libheif Dependency 8.9 high 0.35.4 08 Sep 2026
Critical Memory Vulnerability in Sharp Package: CVE-2026-96889 8.9 high 0.35.5 06 Oct 2026
Vulnerability in sharp package: sharp vulnerability in libwebp dependency CVE-2023-4863 7.8 high 0.32.6 16 Nov 2023
Critical Vulnerabilities in Sharp Package Due to Libvips Dependencies 7.0 high 0.35.0 21 Jul 2026
CVE-2022-29256: Command Injection in sharp Package 6.5 medium 0.30.5 01 Jun 2022

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About sharp

Is sharp safe to use?

Vulert records 5 vulnerabilities for sharp in npm: 0 critical, 4 high, 1 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is sharp's Vulert package health score?

Vulert scores sharp 81/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of sharp affected?

No. 0.35.5, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

Which version of sharp should I use?

0.35.5 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does sharp have?

5 vulnerabilities are recorded for sharp in the npm ecosystem: 0 critical, 4 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new sharp vulnerabilities disclosed?

3 vulnerabilities were recorded for sharp in the last 12 months, and the oldest entry in this database dates to 01 Jun 2022. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of sharp are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor sharp for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the sharp version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.