VulertSecurity VulertSecurity

Vulnerability Database · NuGet · Package report

MimeKit: vulnerability history, versions and safety

MimeKit is a package in the NuGet ecosystem. Vulert records 2 vulnerabilities for it across 114 releases, from Jul 2024 to 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
2 vulnerabilities recorded H1 M1
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 05 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all MimeKit vulnerabilities

Vulert verdict on MimeKit 4.18.2 i

Updated on 23 Oct 2026

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

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

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

  • Current release 4.18.2 — unaffected i
  • Vulnerabilities on record 2 over 1 year · 1 in the last year i
  • Latest disclosure 05 Mar 2026 i
  • Highest CVSS 7.5 i
  • With no published fix 0 i
  • Stars 2,008 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by NuGet, 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 MimeKit, 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.18.2 21 Oct 2026 none MIT — Details →
4.18.1 19 Sep 2026 none MIT — Details →
4.18.0 13 Sep 2026 none MIT — Details →
4.17.0 26 May 2026 none MIT — Details →
4.16.0 15 Apr 2026 none MIT — Details →
4.15.1 05 Mar 2026 none MIT — Details →
4.15.0 14 Feb 2026 M1 MIT Yes Details →
4.14.0 28 Sep 2025 M1 MIT Yes Details →
4.13.0 25 Jun 2025 M1 MIT Yes Details →
4.12.0 29 Apr 2025 M1 MIT Yes Details →
4.11.0 08 Mar 2025 M1 MIT Yes Details →
4.10.0 26 Jan 2025 M1 MIT Yes Details →
4.9.0 09 Dec 2024 M1 MIT Yes Details →
4.8.0 29 Sep 2024 M1 MIT Yes Details →
4.7.1 11 Jul 2024 M1 MIT Yes Details →
4.7.0 29 Jun 2024 H1 M1 MIT Yes Details →
4.6.0 17 May 2024 H1 M1 MIT Yes Details →
4.5.0 13 Apr 2024 H1 M1 MIT Yes Details →
4.4.0 02 Mar 2024 H1 M1 MIT Yes Details →
4.3.0 11 Nov 2023 H1 M1 MIT Yes Details →
4.2.0 02 Sep 2023 H1 M1 MIT Yes Details →
4.1.0 17 Jun 2023 H1 M1 MIT Yes Details →
4.0.0 15 Apr 2023 H1 M1 MIT Yes Details →
3.6.1 19 Mar 2023 H1 M1 MIT Yes Details →
3.6.0 04 Mar 2023 H1 M1 MIT Yes Details →
3.5.0 28 Jan 2023 H1 M1 MIT Yes Details →
3.4.3 25 Nov 2022 H1 M1 MIT Yes Details →
3.4.2 24 Oct 2022 H1 M1 MIT Yes Details →
3.4.1 12 Sep 2022 H1 M1 MIT Yes Details →
3.4.0 18 Aug 2022 H1 M1 MIT Yes Details →
3.3.0 11 Jun 2022 H1 M1 MIT Yes Details →
3.2.0 26 Mar 2022 H1 M1 MIT Yes Details →
3.1.1 30 Jan 2022 H1 M1 MIT Yes Details →
3.1.0 15 Jan 2022 H1 M1 MIT Yes Details →
3.0.0 11 Dec 2021 H1 M1 MIT Yes Details →
2.15.1 13 Sep 2021 M1 MIT Yes Details →
2.15.0 19 Aug 2021 M1 MIT Yes Details →
2.14.0 28 Jul 2021 M1 MIT Yes Details →
2.13.0 12 Jun 2021 M1 MIT Yes Details →
2.12.0 12 May 2021 M1 MIT Yes Details →
2.11.0 12 Mar 2021 M1 MIT Yes Details →
2.10.1 05 Dec 2020 M1 MIT Yes Details →
2.10.0 21 Nov 2020 M1 MIT Yes Details →
2.9.2 12 Sep 2020 M1 MIT Yes Details →
2.9.1 11 Jul 2020 M1 MIT Yes Details →
2.8.0 30 May 2020 M1 MIT Yes Details →
2.7.0 19 May 2020 M1 MIT Yes Details →
2.6.0 04 Apr 2020 M1 MIT Yes Details →
2.5.2 14 Mar 2020 M1 MIT Yes Details →
2.5.1 15 Feb 2020 M1 MIT Yes Details →
2.5.0 18 Jan 2020 M1 MIT Yes Details →
2.4.1 10 Nov 2019 M1 MIT Yes Details →
2.4.0.1 05 Nov 2019 M1 MIT Yes Details →
2.4.0 03 Nov 2019 M1 MIT Yes Details →
2.3.2 12 Oct 2019 M1 MIT Yes Details →
2.3.1 08 Sep 2019 M1 MIT Yes Details →
2.3.0 24 Aug 2019 M1 MIT Yes Details →
2.2.0 11 Jun 2019 M1 MIT Yes Details →
2.1.5.1 13 May 2019 M1 MIT Yes Details →
2.1.4 13 Apr 2019 M1 MIT Yes Details →
2.1.3 24 Feb 2019 M1 MIT Yes Details →
2.1.2 30 Dec 2018 M1 MIT Yes Details →
2.1.1 16 Dec 2018 M1 MIT Yes Details →
2.1.0 01 Dec 2018 M1 non-standard Yes Details →
2.0.7 28 Oct 2018 M1 non-standard Yes Details →
2.0.6 04 Aug 2018 M1 non-standard Yes Details →
2.0.5 07 Jul 2018 M1 non-standard Yes Details →
2.0.4 21 May 2018 M1 non-standard Yes Details →
2.0.3 14 Apr 2018 M1 non-standard Yes Details →
2.0.2 17 Mar 2018 M1 non-standard Yes Details →
2.0.1 06 Jan 2018 M1 non-standard Yes Details →
2.0.0 22 Dec 2017 M1 non-standard Yes Details →
1.22.0 24 Nov 2017 M1 non-standard Yes Details →
1.20.0 28 Oct 2017 M1 non-standard Yes Details →
1.18.1 03 Sep 2017 M1 non-standard Yes Details →
1.18.0 07 Aug 2017 M1 non-standard Yes Details →
1.16.2 01 Jul 2017 M1 non-standard Yes Details →
1.16.1 05 May 2017 M1 non-standard Yes Details →
1.16.0 21 Apr 2017 M1 non-standard Yes Details →
1.14.1 09 Apr 2017 M1 non-standard Yes Details →
1.14.0 09 Apr 2017 M1 non-standard Yes Details →
1.12.0 12 Mar 2017 M1 non-standard Yes Details →
1.10.1 28 Jan 2017 M1 non-standard Yes Details →
1.10.0 31 Oct 2016 M1 non-standard Yes Details →
0.10.0 — M1 non-standard Yes Details →
0.10.1 — M1 non-standard Yes Details →
0.11.0 — M1 non-standard Yes Details →
0.12.0 — M1 non-standard Yes Details →
0.13.0 — M1 non-standard Yes Details →
0.14.0 — M1 non-standard Yes Details →
0.15.0 — M1 non-standard Yes Details →
0.16.0 — M1 non-standard Yes Details →
0.17.0 — M1 non-standard Yes Details →
0.18.0 — M1 non-standard Yes Details →
0.19.0 — M1 non-standard Yes Details →
0.20.0 — M1 non-standard Yes Details →
0.21.0 — M1 non-standard Yes Details →
0.23.0 — M1 non-standard Yes Details →
0.24.0 — M1 non-standard Yes Details →
0.25.0 — M1 non-standard Yes Details →
0.26.0 — M1 — Yes Details →
0.27.0 — M1 — Yes Details →
0.28.0 — M1 — Yes Details →
0.29.0 — M1 — Yes Details →
0.30.0 — M1 — Yes Details →
0.31.0 — M1 — Yes Details →
0.32.0 — M1 — Yes Details →
0.33.0 — M1 — Yes Details →
0.34.0 — M1 — Yes Details →
0.35.0 — M1 — Yes Details →
0.36.0 — M1 — Yes Details →
0.37.0 — M1 — Yes Details →
0.38.0 — M1 — Yes Details →
0.39.0 — M1 — Yes Details →
0.40.0 — M1 — Yes Details →
0.41.0 — M1 — Yes Details →
0.42.0 — M1 — Yes Details →
0.43.0 — M1 — Yes Details →
0.43.0.1 — M1 — Yes Details →
0.5.0 — M1 — Yes Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for MimeKit

The 2 most severe of 2 vulnerabilities recorded for this package

Search all 2 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
Denial of Service Vulnerability in MimeKit 7.5 high 4.7.1 11 Jul 2024
CVE-2026-30227: MimeKit CRLF Injection Vulnerability Leading to SMTP Command Injection and Email Forgery 6.9 medium 4.15.1 05 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 MimeKit

Is MimeKit safe to use?

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

Vulert scores MimeKit 82/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 MimeKit affected?

No. 4.18.2, 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 MimeKit have?

2 vulnerabilities are recorded for MimeKit in the NuGet ecosystem: 0 critical, 1 high, 1 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 MimeKit vulnerabilities disclosed?

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

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