VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

maildev: vulnerability history, versions and safety

maildev is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 18 releases, first recorded in Apr 2024. 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 C1
i
1 with no fix published

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

See the unfixed vulnerabilities →
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 maildev vulnerabilities

Vulert verdict on maildev 3.0.0 i

Updated on 23 Oct 2026

Careful: 3.0.0 has 1 known vulnerability, and 1 has 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 Niche
  • Community Moderate

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 3.0.0 — affected i
  • Vulnerabilities on record 1 over 1 year · 0 in the last year i
  • Latest disclosure 05 Apr 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Stars 6,141 i
  • OpenSSF scorecard 4/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 maildev, 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
3.0.0 23 Sep 2026 C1 MIT No Details →
3.0.0-rc.3 25 Aug 2026 C1 MIT No Details →
3.0.0-rc.2 25 Aug 2026 C1 MIT No Details →
3.0.0-rc.1 06 Jul 2026 C1 MIT No Details →
3.0.0-alpha.0 06 Jul 2026 C1 MIT No Details →
2.2.1 12 Dec 2024 C1 MIT No Details →
2.2.0 12 Dec 2024 C1 MIT No Details →
2.2.0-beta.1 12 Dec 2024 C1 MIT No Details →
2.1.0 20 Jul 2023 C1 MIT No Details →
2.0.5 18 May 2022 C1 MIT No Details →
2.0.4 17 May 2022 C1 MIT No Details →
2.0.3 17 May 2022 C1 MIT No Details →
2.0.2 06 Apr 2022 C1 MIT No Details →
2.0.1 29 Mar 2022 C1 MIT No Details →
2.0.0 29 Mar 2022 C1 MIT No Details →
1.1.1 29 Mar 2022 none MIT — Details →
2.0.0-beta3 30 Mar 2020 C1 MIT No Details →
2.0.0-beta2 29 Mar 2020 C1 MIT No Details →
2.0.0-beta1 26 Mar 2020 C1 MIT No Details →
1.1.0 27 Jul 2019 none MIT — Details →
1.0.0 19 Mar 2019 none MIT — Details →
1.0.0-rc3 04 Jul 2017 none MIT — Details →
1.0.0-rc2 11 May 2017 none MIT — Details →
1.0.0-beta2 11 May 2017 none MIT — Details →
1.0.0-rc1 09 May 2017 none MIT — Details →
0.14.0 13 Aug 2016 none MIT — Details →
0.13.4 01 Jul 2016 none MIT — Details →
0.13.3 16 May 2016 none MIT — Details →
0.13.2 14 May 2016 none MIT — Details →
0.13.1 22 Apr 2016 none MIT — Details →
0.13.0 20 Mar 2016 none MIT — Details →
0.12.2 08 Mar 2016 none MIT — Details →
0.12.1 07 Nov 2015 none MIT — Details →
0.12.0 26 Aug 2015 none MIT — Details →
0.11.0 15 Jul 2015 none MIT — Details →
0.10.0 19 May 2015 none MIT — Details →
0.9.1 29 Mar 2015 none MIT — Details →
0.9.0 06 Mar 2015 none MIT — Details →
0.8.1 27 Feb 2015 none MIT — Details →
0.8.0 25 Feb 2015 none MIT — Details →
0.7.0 12 Jan 2015 none MIT — Details →
0.6.3 22 Dec 2014 none MIT — Details →
0.6.2 21 Nov 2014 none MIT — Details →
0.6.1 25 Oct 2014 none MIT — Details →
0.6.0 05 Oct 2014 none MIT — Details →
0.5.2 06 Jun 2014 none MIT — Details →
0.5.1 22 Mar 2014 none MIT — Details →
0.5.0 06 Jan 2014 none MIT — Details →
0.4.0 02 Dec 2013 none MIT — Details →
0.3.1 08 Oct 2013 none MIT — Details →
0.3.0 04 Sep 2013 none MIT — Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 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 maildev

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-27448: MailDev Remote Code Execution 9.8 critical No fix published 05 Apr 2024

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 maildev

Is maildev safe to use?

Vulert records 1 vulnerabilities for maildev in npm: 1 critical, 0 high, 0 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is maildev's Vulert package health score?

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

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

Which version of maildev should I use?

3.0.0 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 maildev have?

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

0 vulnerabilities were recorded for maildev in the last 12 months, and the oldest entry in this database dates to 05 Apr 2024. 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 maildev 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 maildev for upcoming vulnerabilities?

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