Is MySqlConnector 2.4 vulnerable?

NuGet · 1 release from 2.4.0 to 2.4.0 · latest MySqlConnector is 3.0.0 · checked 18 Nov 2026

Yes: 1 known advisory

Yes. MySqlConnector 2.4.0, the last 2.4 release, is affected by 1 known security advisory (1 medium). Upgrade to 2.6.1 or later to fix all of them.

Upgrade with:dotnet add package MySqlConnector --version 2.6.1

Is your project on an affected MySqlConnector?

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 MySqlConnector 2.4.0

  • MediumGHSA-473q-m89c-ghf828 Oct 2026

    MySqlConnector: Account password disclosed to a man-in-the-middle in zero-configuration TLS mode (clear-text password sent before certificate is verified)

    Affected
    <2.6.1
    Fixed in
    2.6.1

Which of your client projects are still on MySqlConnector 2.4?

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

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