Is MySqlConnector 2.6 vulnerable?
NuGet · 3 releases from 2.6.0 to 2.6.2 · latest MySqlConnector is 3.0.0 · checked 18 Nov 2026
No known advisories in the last release
MySqlConnector 2.6.2, the last 2.6 release, has no known advisories. 1 advisory affects earlier 2.6.x releases, so update to 2.6.2.
dotnet add package MySqlConnector --version 2.6.2Is your project on an affected MySqlConnector?
Look after several .NET apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Fixed within 2.6.x, affecting earlier releases
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
Every MySqlConnector 2.6.x release
Affected: 2.6.0. 2.6.1 and later are not affected. Latest MySqlConnector: 3.0.0.
| Version | Known advisories |
|---|---|
| MySqlConnector 2.6.2 | None |
| MySqlConnector 2.6.1 | None |
| MySqlConnector 2.6.0 | GHSA-473q-m89c-ghf8 |
Which of your client projects are still on MySqlConnector 2.6?
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.