Is MimeKit 3.1 vulnerable?
NuGet · 2 releases from 3.1.0 to 3.1.1 · latest MimeKit is 5.0.0 · checked 18 Nov 2026
Yes: 2 known advisories
Yes. MimeKit 3.1.1, the last 3.1 release, is affected by 2 known security advisories (1 high, 1 medium), including CVE-2026-30227. Upgrade to 4.15.1 or later to fix all of them.
dotnet add package MimeKit --version 4.15.1Is your project on an affected MimeKit?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Advisories affecting MimeKit 3.1.1
MimeKit has CRLF Injection in Quoted Local-Part that Enables SMTP Command Injection and Email Forgery
- Affected
- <4.15.1
- Fixed in
- 4.15.1
Mimekit has vulnerable dependency that can lead to denial of service
- Affected
- >=3.0.0 <4.7.1
- Fixed in
- 4.7.1
Every MimeKit 3.1.x release
Affected: 3.1.0 to 3.1.1. Latest MimeKit: 5.0.0.
| Version | Known advisories |
|---|---|
| MimeKit 3.1.1 | CVE-2026-30227, GHSA-gmc6-fwg3-75m5 |
| MimeKit 3.1.0 | CVE-2026-30227, GHSA-gmc6-fwg3-75m5 |
Which of your client projects are still on MimeKit 3.1?
NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact MimeKit version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.
Other MimeKit versions
Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the NuGet registry. Refreshed daily.