VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mailparser: vulnerability history, versions and safety

mailparser is a package in the npm ecosystem. Vulert records 1 vulnerability for it across 68 releases, first recorded in Mar 2026. 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 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
1 in the last 12 months

Most recent disclosure 03 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mailparser vulnerabilities

Vulert verdict on mailparser 3.12.4 i

Updated on 23 Oct 2026

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

Package health score 80/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Quiet

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

  • Current release 3.12.4 — unaffected i
  • Vulnerabilities on record 1 over 1 year · 1 in the last year i
  • Latest disclosure 03 Mar 2026 i
  • Highest CVSS 6.1 i
  • With no published fix 0 i
  • Stars 1,671 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 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 mailparser, 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.12.4 22 Oct 2026 none MIT — Details →
3.12.3 22 Oct 2026 none MIT — Details →
3.12.2 21 Oct 2026 none MIT — Details →
3.12.1 21 Oct 2026 none MIT — Details →
3.12.0 21 Oct 2026 none MIT — Details →
3.11.0 21 Oct 2026 none MIT — Details →
3.10.0 19 Oct 2026 none MIT — Details →
3.9.47 19 Oct 2026 none MIT — Details →
3.9.46 18 Oct 2026 none MIT — Details →
3.9.45 18 Oct 2026 none MIT — Details →
3.9.44 18 Oct 2026 none MIT — Details →
3.9.43 18 Oct 2026 none MIT — Details →
3.9.42 18 Oct 2026 none MIT — Details →
3.9.41 18 Oct 2026 none MIT — Details →
3.9.40 16 Oct 2026 none MIT — Details →
3.9.39 14 Oct 2026 none MIT — Details →
3.9.38 10 Oct 2026 none MIT — Details →
3.9.37 08 Oct 2026 none MIT — Details →
3.9.36 05 Oct 2026 none MIT — Details →
3.9.35 04 Oct 2026 none MIT — Details →
3.9.34 03 Oct 2026 none MIT — Details →
3.9.33 01 Oct 2026 none MIT — Details →
3.9.32 30 Sep 2026 none MIT — Details →
3.9.31 28 Sep 2026 none MIT — Details →
3.9.30 28 Sep 2026 none MIT — Details →
3.9.29 27 Sep 2026 none MIT — Details →
3.9.28 15 Sep 2026 none MIT — Details →
3.9.27 15 Sep 2026 none MIT — Details →
3.9.26 12 Sep 2026 none MIT — Details →
3.9.25 11 Sep 2026 none MIT — Details →
3.9.24 10 Sep 2026 none MIT — Details →
3.9.23 07 Sep 2026 none MIT — Details →
3.9.22 06 Sep 2026 none MIT — Details →
3.9.21 06 Sep 2026 none MIT — Details →
3.9.20 01 Sep 2026 none MIT — Details →
3.9.19 31 Aug 2026 none MIT — Details →
3.9.18 31 Aug 2026 none MIT — Details →
3.9.17 27 Aug 2026 none MIT — Details →
3.9.16 24 Aug 2026 none MIT — Details →
3.9.15 07 Aug 2026 none MIT — Details →
3.9.14 05 Jul 2026 none MIT — Details →
3.9.13 05 Jul 2026 none MIT — Details →
3.9.12 25 Jun 2026 none MIT — Details →
3.9.11 19 Jun 2026 none MIT — Details →
3.9.10 15 Jun 2026 none MIT — Details →
3.9.9 29 May 2026 none MIT — Details →
3.9.8 08 Apr 2026 none MIT — Details →
3.9.7 08 Apr 2026 none MIT — Details →
3.9.6 25 Mar 2026 none MIT — Details →
3.9.5 23 Mar 2026 none MIT — Details →
3.9.4 09 Mar 2026 none MIT — Details →
3.9.3 28 Jan 2026 none MIT — Details →
3.9.2 28 Jan 2026 L1 MIT Yes Details →
3.9.1 11 Dec 2025 L1 MIT Yes Details →
3.9.0 05 Nov 2025 L1 MIT Yes Details →
3.8.1 05 Nov 2025 L1 MIT Yes Details →
3.7.5 09 Oct 2025 L1 MIT Yes Details →
3.7.4 29 Jun 2025 L1 MIT Yes Details →
3.7.3 20 May 2025 L1 MIT Yes Details →
3.7.2 29 Nov 2024 L1 MIT Yes Details →
3.7.1 25 Apr 2024 L1 MIT Yes Details →
3.7.0 11 Apr 2024 L1 MIT Yes Details →
3.6.9 29 Feb 2024 L1 MIT Yes Details →
3.6.8 29 Feb 2024 L1 MIT Yes Details →
3.6.7 01 Feb 2024 L1 MIT Yes Details →
3.6.6 04 Jan 2024 L1 MIT Yes Details →
3.6.5 01 Jul 2023 L1 MIT Yes Details →
3.6.4 03 Mar 2023 L1 MIT Yes Details →
3.6.3 29 Dec 2022 L1 MIT Yes Details →
3.6.2 15 Dec 2022 L1 MIT Yes Details →
3.6.1 14 Dec 2022 L1 MIT Yes Details →
3.6.0 08 Dec 2022 L1 MIT Yes Details →
3.5.0 28 Apr 2022 L1 MIT Yes Details →
3.4.0 11 Oct 2021 L1 MIT Yes Details →
3.3.3 03 Oct 2021 L1 MIT Yes Details →
3.3.2 01 Oct 2021 L1 MIT Yes Details →
3.3.1 10 Sep 2021 L1 MIT Yes Details →
3.3.0 04 Aug 2021 L1 MIT Yes Details →
3.2.0 02 Apr 2021 L1 MIT Yes Details →
3.1.0 17 Feb 2021 L1 MIT Yes Details →
3.0.1 30 Nov 2020 L1 MIT Yes Details →
3.0.0 07 Sep 2020 L1 EUPL-1.1+ Yes Details →
2.8.1 07 Aug 2020 L1 EUPL-1.1+ OR MIT Yes Details →
2.8.0 22 Jul 2020 L1 EUPL-1.1+ OR MIT Yes Details →
2.7.7 06 Dec 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.7.6 05 Nov 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.7.5 29 Oct 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.7.4 28 Oct 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.7.3 28 Oct 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.7.2 28 Oct 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.7.1 07 May 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.7.0 01 May 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.6.0 27 Mar 2019 L1 EUPL-1.1+ OR MIT Yes Details →
2.5.0 15 Mar 2019 L1 EUPL-1.1+ Yes Details →
2.4.3 16 Nov 2018 L1 EUPL-1.1+ Yes Details →
2.4.2 13 Nov 2018 L1 EUPL-1.1+ Yes Details →
2.4.1 13 Nov 2018 L1 EUPL-1.1+ Yes Details →
2.4.0 23 Oct 2018 L1 EUPL-1.1+ Yes Details →
2.3.4 02 Sep 2018 L1 EUPL-1.1+ Yes Details →
2.3.3 22 Aug 2018 L1 EUPL-1.1+ Yes Details →
2.3.2 24 Jul 2018 L1 — Yes Details →
2.3.1 24 Jul 2018 L1 — Yes Details →
2.3.0 24 Jul 2018 L1 — Yes Details →
2.2.0 08 Feb 2018 L1 — Yes Details →
2.1.0 03 Oct 2017 L1 — Yes Details →
2.0.5 03 May 2017 L1 — Yes Details →
2.0.4 17 Apr 2017 L1 — Yes Details →
2.0.3 07 Apr 2017 L1 — Yes Details →
2.0.2 22 Feb 2017 L1 — Yes Details →
2.0.1 03 Feb 2017 L1 — Yes Details →
2.0.0 02 Feb 2017 L1 — Yes Details →
0.6.2 22 Jan 2017 L1 — Yes Details →
0.6.1 04 Jul 2016 L1 — Yes Details →
0.6.0 02 Jun 2016 L1 — Yes Details →
0.5.3 02 Nov 2015 L1 — Yes Details →
0.5.2 20 Jul 2015 L1 — Yes Details →
0.5.1 30 Apr 2015 L1 — Yes Details →
0.5.0 11 Apr 2015 L1 — Yes Details →
0.4.9 25 Feb 2015 L1 — Yes Details →
0.4.8 14 Jan 2015 L1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for mailparser

The 1 most severe of 1 vulnerabilities recorded for this package

Search all 1 in the database →
Vulnerability Severity Fixed version ↑ Disclosed ↑
CVE-2026-3455: mailparser Vulnerable to Cross-site Scripting (XSS) 6.1 low 3.9.3 03 Mar 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 mailparser

Is mailparser safe to use?

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

Vulert scores mailparser 80/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 mailparser affected?

No. 3.12.4, 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 mailparser have?

1 vulnerability is recorded for mailparser in the npm ecosystem: 0 critical, 0 high, 0 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mailparser vulnerabilities disclosed?

1 vulnerability was recorded for mailparser in the last 12 months, and the oldest entry in this database dates to 03 Mar 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 mailparser 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 mailparser for upcoming vulnerabilities?

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