Vulnerability Database · npm · Package report

exifreader: vulnerability history, versions and safety

exifreader is a package in the npm ecosystem. Vulert records 4 vulnerabilities for it across 102 releases, from May 2026 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
4 vulnerabilities recorded H2 M2
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
4 in the last 12 months

Most recent disclosure 17 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on exifreader 4.51.0 i

Updated on 23 Oct 2026

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

Package health score 74/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Moderate

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

  • Current release 4.51.0 — unaffected i
  • Vulnerabilities on record 4 over 1 year · 4 in the last year i
  • Latest disclosure 17 Sep 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 110 packages i
  • Stars 1,003 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MPL-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 exifreader, 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
4.51.0 21 Oct 2026 none MPL-2.0 — Details →
4.50.0 12 Oct 2026 none MPL-2.0 — Details →
4.49.0 11 Oct 2026 none MPL-2.0 — Details →
4.48.1 10 Oct 2026 none MPL-2.0 — Details →
4.48.0 09 Oct 2026 none MPL-2.0 — Details →
4.47.0 08 Oct 2026 none MPL-2.0 — Details →
4.46.0 26 Sep 2026 none MPL-2.0 — Details →
4.45.2 21 Sep 2026 none MPL-2.0 — Details →
4.45.1 18 Sep 2026 none MPL-2.0 — Details →
4.45.0 10 Sep 2026 none MPL-2.0 — Details →
4.44.1 05 Sep 2026 none MPL-2.0 — Details →
4.44.0 21 Aug 2026 none MPL-2.0 — Details →
4.43.0 16 Aug 2026 none MPL-2.0 — Details →
4.42.0 05 Aug 2026 none MPL-2.0 — Details →
4.41.4 05 Aug 2026 none MPL-2.0 — Details →
4.41.3 18 Jul 2026 none MPL-2.0 — Details →
4.41.2 18 Jul 2026 none MPL-2.0 — Details →
4.41.1 18 Jul 2026 none MPL-2.0 — Details →
4.41.0 08 Jun 2026 H1 MPL-2.0 Yes Details →
4.40.5 03 Jun 2026 H1 MPL-2.0 Yes Details →
4.40.4 03 Jun 2026 H1 MPL-2.0 Yes Details →
4.40.3 31 May 2026 H1 MPL-2.0 Yes Details →
4.40.2 30 May 2026 H1 MPL-2.0 Yes Details →
4.40.1 30 May 2026 H1 MPL-2.0 Yes Details →
4.40.0 29 May 2026 H1 M1 MPL-2.0 Yes Details →
4.39.1 19 May 2026 H1 M1 MPL-2.0 Yes Details →
4.39.0 15 May 2026 H1 M1 MPL-2.0 Yes Details →
4.38.1 09 Apr 2026 H2 M2 MPL-2.0 Yes Details →
4.38.0 07 Apr 2026 H2 M2 MPL-2.0 Yes Details →
4.37.1 05 Apr 2026 H2 M2 MPL-2.0 Yes Details →
4.37.0 11 Mar 2026 H2 M2 MPL-2.0 Yes Details →
4.36.2 19 Feb 2026 H2 M2 MPL-2.0 Yes Details →
4.36.1 25 Jan 2026 H2 M2 MPL-2.0 Yes Details →
4.36.0 11 Jan 2026 H2 M2 MPL-2.0 Yes Details →
4.35.0 09 Jan 2026 H2 M2 MPL-2.0 Yes Details →
4.34.0 05 Jan 2026 H2 M2 MPL-2.0 Yes Details →
4.33.1 05 Dec 2025 H2 M2 MPL-2.0 Yes Details →
4.32.0 20 Sep 2025 H2 M2 MPL-2.0 Yes Details →
4.31.2 29 Aug 2025 H2 M2 MPL-2.0 Yes Details →
4.31.1 17 Jun 2025 H2 M2 MPL-2.0 Yes Details →
4.31.0 27 May 2025 H2 M2 MPL-2.0 Yes Details →
4.30.1 08 May 2025 H2 M2 MPL-2.0 Yes Details →
4.30.0 01 May 2025 H2 M2 MPL-2.0 Yes Details →
4.29.0 21 Apr 2025 H2 M2 MPL-2.0 Yes Details →
4.28.1 09 Apr 2025 H2 M2 MPL-2.0 Yes Details →
4.28.0 07 Apr 2025 H2 M2 MPL-2.0 Yes Details →
4.27.0 24 Mar 2025 H2 M2 MPL-2.0 Yes Details →
4.26.2 05 Mar 2025 H2 M2 MPL-2.0 Yes Details →
4.26.1 26 Jan 2025 H2 M2 MPL-2.0 Yes Details →
4.26.0 25 Dec 2024 H2 M2 MPL-2.0 Yes Details →
4.25.0 28 Oct 2024 H2 M2 MPL-2.0 Yes Details →
4.24.0 25 Oct 2024 H2 M2 MPL-2.0 Yes Details →
4.23.7 07 Oct 2024 H2 M2 MPL-2.0 Yes Details →
4.23.6 04 Oct 2024 H2 M2 MPL-2.0 Yes Details →
4.23.5 05 Sep 2024 H2 M2 MPL-2.0 Yes Details →
4.23.4 05 Sep 2024 H2 M2 MPL-2.0 Yes Details →
4.23.3 12 Jun 2024 H2 M2 MPL-2.0 Yes Details →
4.23.2 29 May 2024 H2 M2 MPL-2.0 Yes Details →
4.23.1 04 May 2024 H2 M2 MPL-2.0 Yes Details →
4.22.1 08 Apr 2024 H2 M2 MPL-2.0 Yes Details →
4.22.0 06 Apr 2024 H2 M2 MPL-2.0 Yes Details →
4.21.1 10 Mar 2024 H2 M2 MPL-2.0 Yes Details →
4.21.0 04 Feb 2024 H2 M2 MPL-2.0 Yes Details →
4.20.0 28 Dec 2023 H2 M2 MPL-2.0 Yes Details →
4.19.1 18 Dec 2023 H2 M1 MPL-2.0 Yes Details →
4.19.0 17 Dec 2023 H2 M1 MPL-2.0 Yes Details →
4.18.0 16 Dec 2023 H2 M1 MPL-2.0 Yes Details →
4.17.0 19 Nov 2023 H2 M1 MPL-2.0 Yes Details →
4.16.0 31 Oct 2023 H2 M1 MPL-2.0 Yes Details →
4.15.0 26 Oct 2023 H2 M1 MPL-2.0 Yes Details →
4.14.1 21 Oct 2023 H2 M1 MPL-2.0 Yes Details →
4.14.0 21 Oct 2023 H2 M1 MPL-2.0 Yes Details →
4.13.2 07 Oct 2023 H2 M1 MPL-2.0 Yes Details →
4.13.1 03 Oct 2023 H2 M1 MPL-2.0 Yes Details →
4.13.0 06 Jul 2023 H2 M1 MPL-2.0 Yes Details →
4.12.1 09 Jun 2023 H2 M1 MPL-2.0 Yes Details →
4.12.0 28 Mar 2023 H2 M1 MPL-2.0 Yes Details →
4.11.1 17 Mar 2023 H2 M1 MPL-2.0 Yes Details →
4.11.0 13 Mar 2023 H2 M1 MPL-2.0 Yes Details →
4.10.0 10 Mar 2023 H2 M1 MPL-2.0 Yes Details →
4.9.2 26 Feb 2023 H2 M1 MPL-2.0 Yes Details →
4.9.1 19 Dec 2022 H2 M1 MPL-2.0 Yes Details →
4.9.0 12 Dec 2022 H2 M1 MPL-2.0 Yes Details →
4.8.1 08 Nov 2022 H2 M1 MPL-2.0 Yes Details →
4.8.0 07 Nov 2022 H2 M1 MPL-2.0 Yes Details →
4.7.0 04 Nov 2022 H2 M1 MPL-2.0 Yes Details →
4.6.0 01 Oct 2022 H2 M1 MPL-2.0 Yes Details →
4.5.1 02 Aug 2022 H2 M1 MPL-2.0 Yes Details →
4.5.0 12 Apr 2022 H2 M1 MPL-2.0 Yes Details →
4.4.0 12 Mar 2022 H2 M1 MPL-2.0 Yes Details →
4.3.1 11 Mar 2022 H2 M1 MPL-2.0 Yes Details →
4.3.0 04 Mar 2022 H2 M1 MPL-2.0 Yes Details →
4.2.0 23 Jan 2022 H2 M1 MPL-2.0 Yes Details →
4.1.1 30 Dec 2021 H2 M1 MPL-2.0 Yes Details →
4.1.0 21 Nov 2021 H2 M1 MPL-2.0 Yes Details →
4.0.0 31 Oct 2021 H2 M1 MPL-2.0 Yes Details →
3.16.0 06 Jun 2021 H2 M1 MPL-2.0 Yes Details →
3.15.0 25 Apr 2021 H2 M1 MPL-2.0 Yes Details →
3.14.1 13 Mar 2021 H2 M1 MPL-2.0 Yes Details →
3.14.0 31 Jan 2021 H2 M1 MPL-2.0 Yes Details →
3.13.0 30 Dec 2020 H2 M1 — Yes Details →
3.12.6 23 Nov 2020 H2 M1 — Yes Details →
3.12.5 21 Nov 2020 H2 M1 — Yes Details →
3.12.4 21 Nov 2020 H2 M1 — Yes Details →
3.12.3 10 Oct 2020 H2 M1 — Yes Details →
3.12.2 19 Aug 2020 H2 M1 — Yes Details →
3.12.1 17 Aug 2020 H2 M1 — Yes Details →
3.12.0 01 Jun 2020 H2 M1 — Yes Details →
3.11.2 09 May 2020 H2 M1 — Yes Details →
3.11.1 08 May 2020 H2 M1 — Yes Details →
3.11.0 02 May 2020 H2 M1 — Yes Details →
3.10.0 01 May 2020 H2 M1 — Yes Details →
3.9.0 19 Apr 2020 H2 M1 — Yes Details →
3.8.0 14 Apr 2020 H2 M1 — Yes Details →
3.7.0 11 Apr 2020 H2 M1 — Yes Details →
3.6.1 10 Apr 2020 H2 M1 — Yes Details →
3.6.0 06 Apr 2020 H2 M1 — Yes Details →
3.5.0 01 Apr 2020 H2 M1 — Yes Details →
3.4.0 31 Mar 2020 H2 M1 — Yes Details →
3.3.0 28 Mar 2020 H2 M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 4

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

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 exifreader

Is exifreader safe to use?

Vulert records 4 vulnerabilities for exifreader in npm: 0 critical, 2 high, 2 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 exifreader's Vulert package health score?

Vulert scores exifreader 74/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 exifreader affected?

No. 4.51.0, 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.

How many vulnerabilities does exifreader have?

4 vulnerabilities are recorded for exifreader in the npm ecosystem: 0 critical, 2 high, 2 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 exifreader vulnerabilities disclosed?

4 vulnerabilities were recorded for exifreader in the last 12 months, and the oldest entry in this database dates to 29 May 2026. 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 exifreader 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 exifreader for upcoming vulnerabilities?

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