VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mime: vulnerability history, versions and safety

mime is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 3 releases, first recorded in Jul 2018. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
1 vulnerabilities recorded H1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mime vulnerabilities

Vulert verdict on mime 4.1.1 i

Updated on 22 Oct 2026

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

Package health score 81/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 4.1.1 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 20 Jul 2018 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Depended on by 7,529 packages i
  • Stars 2,359 i
  • OpenSSF scorecard 3/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 mime, 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.1.1 12 Oct 2026 none MIT — Details →
4.1.0 12 Sep 2025 none MIT — Details →
4.0.7 03 Apr 2025 none MIT — Details →
4.0.6 17 Dec 2024 none MIT — Details →
4.0.5 17 Dec 2024 none MIT — Details →
4.0.4 06 Jul 2024 none MIT — Details →
4.0.3 25 Apr 2024 none MIT — Details →
4.0.2 24 Apr 2024 none MIT — Details →
4.0.1 17 Dec 2023 none MIT — Details →
4.0.0 29 Nov 2023 none MIT — Details →
4.0.0-beta.1 14 Sep 2023 none MIT — Details →
4.0.0-beta.0 13 Sep 2023 none MIT — Details →
3.0.0 03 Nov 2021 none MIT — Details →
2.6.0 02 Nov 2021 none MIT — Details →
2.5.2 17 Feb 2021 none MIT — Details →
2.5.0 16 Jan 2021 none MIT — Details →
2.4.7 16 Dec 2020 none MIT — Details →
2.4.6 27 May 2020 none MIT — Details →
2.4.5 01 May 2020 none MIT — Details →
2.4.4 07 Jun 2019 none MIT — Details →
2.4.3 15 May 2019 none MIT — Details →
2.4.2 07 Apr 2019 none MIT — Details →
2.4.1 03 Apr 2019 none MIT — Details →
2.4.0 26 Nov 2018 none MIT — Details →
2.3.1 11 Apr 2018 none MIT — Details →
2.3.0 11 Apr 2018 none MIT — Details →
2.2.2 30 Mar 2018 none MIT — Details →
2.2.1 30 Mar 2018 none MIT — Details →
2.2.0 04 Jan 2018 none MIT — Details →
2.1.0 22 Dec 2017 none MIT — Details →
2.0.5 22 Dec 2017 none MIT — Details →
1.6.0 25 Nov 2017 none MIT — Details →
1.5.0 22 Nov 2017 none MIT — Details →
2.0.3 25 Sep 2017 none MIT — Details →
1.4.1 25 Sep 2017 none MIT — Details →
2.0.2 18 Sep 2017 H1 MIT Yes Details →
2.0.1 13 Sep 2017 H1 MIT Yes Details →
2.0.0 13 Sep 2017 H1 MIT Yes Details →
1.4.0 28 Aug 2017 none MIT — Details →
1.3.6 12 May 2017 none MIT — Details →
1.3.5 11 May 2017 none MIT — Details →
1.3.4 07 Feb 2015 none MIT — Details →
1.3.3 07 Feb 2015 none MIT — Details →
1.3.2 05 Feb 2015 none MIT — Details →
1.3.0 05 Feb 2015 none MIT — Details →
1.2.11 15 Aug 2013 none MIT — Details →
1.2.10 25 Jul 2013 none MIT — Details →
1.2.9 17 Jan 2013 none MIT — Details →
1.2.8 10 Jan 2013 none MIT — Details →
1.2.7 19 Jul 2012 none MIT — Details →
1.2.6 26 Jun 2012 none MIT — Details →
1.2.5 16 Feb 2012 none MIT — Details →
1.2.4 18 Sep 2011 none MIT — Details →
1.2.3 07 Sep 2011 none MIT — Details →
1.2.2 09 May 2011 none MIT — Details →
1.0.0 20 Jan 2011 none MIT — Details →
1.1.0 20 Jan 2011 none MIT — Details →
1.2.1 20 Jan 2011 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1

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

03 Vulnerabilities

Recorded vulnerabilities for mime

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
mime Regular Expression Denial of Service when MIME lookup performed on untrusted user input 7.5 high 2.0.3 20 Jul 2018

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 mime

Is mime safe to use?

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

Vulert scores mime 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 mime affected?

No. 4.1.1, 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 mime have?

1 vulnerability is recorded for mime in the npm ecosystem: 0 critical, 1 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 mime vulnerabilities disclosed?

0 vulnerabilities were recorded for mime in the last 12 months, and the oldest entry in this database dates to 20 Jul 2018. 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 mime 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 mime for upcoming vulnerabilities?

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