Is mysql2 3.10 vulnerable?

npm · 4 releases from 3.10.0 to 3.10.3 · latest mysql2 is 3.24.6 · checked 2 Nov 2026

Yes: 2 known advisories

Yes. mysql2 3.10.3, the last 3.10 release, is affected by 2 known security advisories (1 high, 1 medium). Upgrade to 3.23.1 or later to fix all of them.

Upgrade with:npm install mysql2@3.23.1

Is your project affected?

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

Advisories affecting mysql2 3.10.3

  • HighGHSA-3f6p-5ww8-9rcr1 Sept 2026

    MySQL2: Auth Plugin Downgrade to mysql_clear_password Leaks Plaintext Credentials

    Affected
    <3.22.0
    Fixed in
    3.22.0
  • MediumGHSA-rgwj-5xj2-c3m331 Aug 2026

    MySQL2: Unbounded zlib inflate in compressed MySQL protocol handler allows decompression-bomb DoS

    Affected
    <3.23.1
    Fixed in
    3.23.1

Which of your client projects are still on mysql2 3.10?

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

Scan a project free, no signupOr connect GitHub to scan every repo

Other mysql2 versions

Advisory data from OSV.dev (opens OSV.dev in a new tab), which includes the GitHub Advisory Database. Release list from the npm registry. Refreshed daily.