VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

image-size: vulnerability history, versions and safety

image-size is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 73 releases, from Apr 2025 to Jun 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded H3
i
2 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
2 in the last 12 months

Most recent disclosure 10 Jun 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all image-size vulnerabilities

Vulert verdict on image-size 2.0.4 i

Updated on 23 Oct 2026

Careful: 2.0.4 has 2 known vulnerabilities, and 2 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

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

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 2.0.4 — affected i
  • Vulnerabilities on record 3 over 1 year · 2 in the last year i
  • Latest disclosure 10 Jun 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 2 i
  • Depended on by 1,543 packages i
  • Stars 2,228 i
  • OpenSSF scorecard 2/10 i
  • Last release 1 month ago i
  • Licence MIT 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 image-size, 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
2.0.4 14 Sep 2026 H2 MIT No Details →
2.0.3 14 Sep 2026 H2 MIT No Details →
1.2.1 02 Apr 2025 H2 MIT No Details →
2.0.2 02 Apr 2025 H2 MIT No Details →
2.0.1 13 Mar 2025 H2 MIT No Details →
2.0.0 25 Feb 2025 H2 MIT No Details →
2.0.0-beta.4 25 Dec 2024 H2 MIT No Details →
1.2.0 22 Dec 2024 H3 MIT No Details →
2.0.0-beta.2 12 Jan 2024 H2 MIT No Details →
1.1.1 02 Jan 2024 H3 MIT No Details →
1.1.0 28 Dec 2023 H3 MIT No Details →
2.0.0-beta.1 13 Nov 2023 H2 MIT No Details →
2.0.0-beta 13 Nov 2023 H2 MIT No Details →
2.0.0-alpha.2 13 Nov 2023 H2 MIT No Details →
2.0.0-alpha.1 21 Mar 2023 H2 MIT No Details →
1.0.2 12 Jul 2022 H2 MIT No Details →
1.0.1 10 Jan 2022 H2 MIT No Details →
1.0.0 14 Apr 2021 H2 MIT No Details →
0.9.7 15 Mar 2021 H2 MIT No Details →
0.9.6 15 Mar 2021 H2 MIT No Details →
0.9.5 11 Mar 2021 H2 MIT No Details →
0.9.4 24 Feb 2021 H2 MIT No Details →
0.9.3 26 Oct 2020 H2 MIT No Details →
0.9.2 19 Oct 2020 H2 MIT No Details →
0.9.1 03 Sep 2020 H2 MIT No Details →
0.8.3 30 Sep 2019 H2 MIT No Details →
0.8.2 23 Sep 2019 H2 MIT No Details →
0.8.1 17 Sep 2019 H2 MIT No Details →
0.8.0 17 Sep 2019 H2 MIT No Details →
0.7.5 14 Sep 2019 H2 MIT No Details →
0.7.4 23 Apr 2019 H2 MIT No Details →
0.7.3 02 Apr 2019 H2 MIT No Details →
0.7.2 15 Feb 2019 H2 MIT No Details →
0.7.1 08 Jan 2019 H2 MIT No Details →
0.7.0 08 Jan 2019 H2 MIT No Details →
0.6.3 13 Jun 2018 H2 MIT No Details →
0.6.2 16 Dec 2017 H2 MIT No Details →
0.6.1 19 Jul 2017 H2 MIT No Details →
0.6.0 26 Jun 2017 H2 MIT No Details →
0.5.5 12 Jun 2017 H2 MIT No Details →
0.5.4 15 May 2017 H2 MIT No Details →
0.5.3 11 May 2017 H2 MIT No Details →
0.5.2 09 May 2017 H2 MIT No Details →
0.5.1 25 Dec 2016 H2 MIT No Details →
0.5.0 22 Mar 2016 H2 MIT No Details →
0.4.0 23 Nov 2015 H2 MIT No Details →
0.3.5 16 Oct 2014 H2 MIT No Details →
0.3.3 09 Sep 2014 H2 MIT No Details →
0.3.2 15 Jul 2014 H2 MIT No Details →
0.3.1 11 Jul 2014 H2 MIT No Details →
0.3.0 09 Jun 2014 H2 MIT No Details →
0.2.5 14 May 2014 H2 MIT No Details →
0.2.4 09 May 2014 H2 MIT No Details →
0.2.3 26 Mar 2014 H2 MIT No Details →
0.2.2 19 Mar 2014 H2 MIT No Details →
0.2.1 22 Jan 2014 H2 MIT No Details →
0.1.20 22 Jan 2014 H2 MIT No Details →
0.1.17 22 Jan 2014 H2 MIT No Details →
0.1.16 03 Dec 2013 H2 MIT No Details →
0.0.16 20 Nov 2013 H2 MIT No Details →
0.1.15 17 Nov 2013 H2 MIT No Details →
0.1.10 11 Oct 2013 H2 MIT No Details →
0.1.7 11 Oct 2013 H2 MIT No Details →
0.1.6 11 Oct 2013 H2 MIT No Details →
0.1.5 05 Jul 2013 H2 MIT No Details →
0.1.4 05 Jul 2013 H2 MIT No Details →
0.1.3 04 Jul 2013 H2 MIT No Details →
0.1.2 04 Jul 2013 H2 MIT No Details →
0.1.1 03 Jul 2013 H2 MIT No Details →
0.1.0 03 Jul 2013 H2 MIT No Details →
0.0.5 03 Jul 2013 H2 MIT No Details →
0.0.3 02 Jul 2013 H2 MIT No Details →
0.0.2 02 Jul 2013 H2 MIT No Details →

All 73 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2025 1
  • 2026 2

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

03 Vulnerabilities

Recorded vulnerabilities for image-size

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in image-size Package 7.5 high 1.2.1 02 Apr 2025
CVE-2025-71329: image-size Package Denial of Service Vulnerability via Infinite Loops 7.5 high No fix published 10 Jun 2026
CVE-2025-71330: image-size Package Denial of Service Vulnerability via ICNS Parser 7.5 high No fix published 10 Jun 2026

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 image-size

Is image-size safe to use?

Vulert records 3 vulnerabilities for image-size in npm: 0 critical, 3 high, 0 medium and 0 low. 2 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is image-size's Vulert package health score?

Vulert scores image-size 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of image-size affected?

Yes. 2.0.4, the version you would install today, has 2 known vulnerabilities, and 2 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of image-size should I use?

2.0.4 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 image-size have?

3 vulnerabilities are recorded for image-size in the npm ecosystem: 0 critical, 3 high, 0 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 image-size vulnerabilities disclosed?

2 vulnerabilities were recorded for image-size in the last 12 months, and the oldest entry in this database dates to 02 Apr 2025. 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 image-size 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 image-size for upcoming vulnerabilities?

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