Is MailKit 2.5 vulnerable?

NuGet · 3 releases from 2.5.0 to 2.5.2 · latest MailKit is 5.0.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. MailKit 2.5.2, the last 2.5 release, is affected by 1 known security advisory (1 medium), including CVE-2026-41319. Upgrade to 4.16.0 or later to fix all of them.

Upgrade with:dotnet add package MailKit --version 4.16.0

Is your project on an affected MailKit?

Private repo? Upload its lockfile instead, or connect GitHub to check every repo.

Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie

Advisories affecting MailKit 2.5.2

  • MediumCVE-2026-41319GHSA-9j88-vvj5-vhgr18 Apr 2026

    MailKit has STARTTLS Response Injection via unflushed stream buffer that enables SASL mechanism downgrade

    Affected
    <4.16.0
    Fixed in
    4.16.0

Every MailKit 2.5.x release

Affected: 2.5.0 to 2.5.2. Latest MailKit: 5.0.0.

VersionKnown advisories
MailKit 2.5.2CVE-2026-41319
MailKit 2.5.1CVE-2026-41319
MailKit 2.5.0CVE-2026-41319

Which of your client projects are still on MailKit 2.5?

NPMscan reads the lockfiles in every GitHub repo you pick, finds the exact MailKit version each one installs, and checks it against these advisories. Each finding comes with the command that fixes it.

Other MailKit 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.