VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mysql2: vulnerability history, versions and safety

mysql2 is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 86 releases, from Apr 2024 to Sep 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded C2 H2 M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
2 in the last 12 months

Most recent disclosure 01 Sep 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mysql2 vulnerabilities

Vulert verdict on mysql2 3.24.6 i

Updated on 23 Oct 2026

Good news: 3.24.6, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 79/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Key ecosystem project
  • Community Moderate

What to do: Stay on 3.24.6 or newer. This can change: a vulnerability disclosed tomorrow can affect 3.24.6 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 3.24.6 — unaffected i
  • Vulnerabilities on record 7 over 2 years · 2 in the last year i
  • Latest disclosure 01 Sep 2026 i
  • Highest CVSS 9.8 i
  • With no published fix 0 i
  • Depended on by 6,808 packages i
  • Stars 4,389 i
  • OpenSSF scorecard 5/10 i
  • Last release this month i
  • Licence MIT i
  • Similar names mysql i

Version list, release dates, licence and dependants published by the npm registry, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for mysql2, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
3.24.6 13 Oct 2026 none MIT — Details →
3.24.6-canary.8c068ef 06 Oct 2026 none MIT — Details →
3.24.5 29 Sep 2026 none MIT — Details →
3.24.5-canary.b1c39c8 29 Sep 2026 none MIT — Details →
3.24.4 08 Sep 2026 none MIT — Details →
3.24.4-canary.e5833be 07 Sep 2026 none MIT — Details →
3.24.4-canary.2387daf 06 Sep 2026 none MIT — Details →
3.24.4-canary.9178c82 06 Sep 2026 none MIT — Details →
3.24.3 02 Sep 2026 none MIT — Details →
3.24.3-canary.1281e1e 30 Aug 2026 none MIT — Details →
3.24.2 24 Aug 2026 none MIT — Details →
3.24.2-canary.87579e1 24 Aug 2026 none MIT — Details →
3.24.2-canary.1dcd8ef 24 Aug 2026 none MIT — Details →
3.24.2-canary.de56272 24 Aug 2026 none MIT — Details →
3.24.1 24 Aug 2026 none MIT — Details →
3.24.1-canary.183e947 24 Aug 2026 none MIT — Details →
3.24.0 23 Aug 2026 none MIT — Details →
3.23.5-canary.f3a60bc 23 Aug 2026 none MIT — Details →
3.23.5-canary.c86fe5a 23 Aug 2026 none MIT — Details →
3.23.5-canary.8ec20f1 23 Aug 2026 none MIT — Details →
3.23.5-canary.5bf7bda 23 Aug 2026 none MIT — Details →
3.23.4 20 Aug 2026 none MIT — Details →
3.23.4-canary.3cccf4a 19 Aug 2026 none MIT — Details →
3.23.4-canary.8b1f829 10 Aug 2026 none MIT — Details →
3.23.3 10 Aug 2026 none MIT — Details →
3.23.3-canary.88f3d9e 10 Aug 2026 none MIT — Details →
3.23.3-canary.361d232 09 Aug 2026 none MIT — Details →
3.23.3-canary.20f732b 09 Aug 2026 none MIT — Details →
3.23.3-canary.508a731 09 Aug 2026 none MIT — Details →
3.23.3-canary.7ce6943 09 Aug 2026 none MIT — Details →
3.23.2 27 Jul 2026 none MIT — Details →
3.23.2-canary.fbd64b6 24 Jul 2026 none MIT — Details →
3.23.2-canary.f64ce07 22 Jul 2026 none MIT — Details →
3.23.1 19 Jul 2026 none MIT — Details →
3.23.1-canary.01f1092 19 Jul 2026 M1 MIT Yes Details →
3.23.1-canary.7c48343 19 Jul 2026 M1 MIT Yes Details →
3.23.0 14 Jul 2026 M1 MIT Yes Details →
3.22.7-canary.6b933f6 13 Jul 2026 M1 MIT Yes Details →
3.22.7-canary.a26ff14 11 Jul 2026 M1 MIT Yes Details →
3.22.7-canary.5034e57 10 Jul 2026 M1 MIT Yes Details →
3.22.6 07 Jul 2026 M1 MIT Yes Details →
3.22.6-canary.1b927a9 07 Jul 2026 M1 MIT Yes Details →
3.22.5 06 Jun 2026 M1 MIT Yes Details →
3.22.5-canary.2af33a1 06 Jun 2026 M1 MIT Yes Details →
3.22.4 26 May 2026 M1 MIT Yes Details →
3.22.3 27 Apr 2026 M1 MIT Yes Details →
3.22.3-canary.e72f923d 23 Apr 2026 M1 MIT Yes Details →
3.22.2 21 Apr 2026 M1 MIT Yes Details →
3.22.2-canary.c79a3f32 20 Apr 2026 M1 MIT Yes Details →
3.22.1 17 Apr 2026 M1 MIT Yes Details →
3.22.1-canary.5b6206c8 17 Apr 2026 M1 MIT Yes Details →
3.22.1-canary.cb5adccb 10 Apr 2026 M1 MIT Yes Details →
3.22.0 10 Apr 2026 M1 MIT Yes Details →
3.21.2-canary.ab131de5 10 Apr 2026 H1 M1 MIT Yes Details →
3.21.2-canary.49a64cca 10 Apr 2026 H1 M1 MIT Yes Details →
3.21.2-canary.884bec56 10 Apr 2026 H1 M1 MIT Yes Details →
3.21.1 10 Apr 2026 H1 M1 MIT Yes Details →
3.21.1-canary.e1930b80 09 Apr 2026 H1 M1 MIT Yes Details →
3.21.1-canary.295264b2 09 Apr 2026 H1 M1 MIT Yes Details →
3.21.0 09 Apr 2026 H1 M1 MIT Yes Details →
3.20.1-canary.d732f780 09 Apr 2026 H1 M1 MIT Yes Details →
3.20.1-canary.2bdc12a4 09 Apr 2026 H1 M1 MIT Yes Details →
3.20.1-canary.9fafd6f7 09 Apr 2026 H1 M1 MIT Yes Details →
3.20.0 15 Mar 2026 H1 M1 MIT Yes Details →
3.19.2-canary.5ac5563c 15 Mar 2026 H1 M1 MIT Yes Details →
3.19.2-canary.7e57db62 15 Mar 2026 H1 M1 MIT Yes Details →
3.19.2-canary.f4ce16ab 15 Mar 2026 H1 M1 MIT Yes Details →
3.19.2-canary.97855a60 15 Mar 2026 H1 M1 MIT Yes Details →
3.19.2-canary.90a06776 14 Mar 2026 H1 M1 MIT Yes Details →
3.19.2-canary.c06afc25 14 Mar 2026 H1 M1 MIT Yes Details →
3.19.1 09 Mar 2026 H1 M1 MIT Yes Details →
3.19.1-canary.18692157 09 Mar 2026 H1 M1 MIT Yes Details →
3.19.1-canary.3123b4e6 08 Mar 2026 H1 M1 MIT Yes Details →
3.19.1-canary.91c5229d 08 Mar 2026 H1 M1 MIT Yes Details →
3.19.1-canary.7c2ae002 08 Mar 2026 H1 M1 MIT Yes Details →
3.19.0 05 Mar 2026 H1 M1 MIT Yes Details →
3.18.3-canary.b57c671c 03 Mar 2026 H1 M1 MIT Yes Details →
3.18.3-canary.099beeae 02 Mar 2026 H1 M1 MIT Yes Details →
3.18.2 26 Feb 2026 H1 M1 MIT Yes Details →
3.18.2-canary.3f94950d 26 Feb 2026 H1 M1 MIT Yes Details →
3.18.2-canary.bde9aec8 26 Feb 2026 H1 M1 MIT Yes Details →
3.18.2-canary.2ad5f0b2 26 Feb 2026 H1 M1 MIT Yes Details →
3.18.2-canary.b274e725 26 Feb 2026 H1 M1 MIT Yes Details →
3.18.1 25 Feb 2026 H1 M1 MIT Yes Details →
3.18.1-canary.3f4bbca3 25 Feb 2026 H1 M1 MIT Yes Details →
3.18.0 23 Feb 2026 H1 M1 MIT Yes Details →
3.17.6-canary.1e612dc6 23 Feb 2026 H1 M1 MIT Yes Details →
3.17.5 23 Feb 2026 H1 M1 MIT Yes Details →
3.17.5-canary.8aa20522 21 Feb 2026 H1 M1 MIT Yes Details →
3.17.5-canary.0e06e02e 21 Feb 2026 H1 M1 MIT Yes Details →
3.17.5-canary.5f8ac971 20 Feb 2026 H1 M1 MIT Yes Details →
3.17.5-canary.c4efc90a 20 Feb 2026 H1 M1 MIT Yes Details →
3.17.4 20 Feb 2026 H1 M1 MIT Yes Details →
3.17.3 19 Feb 2026 H1 M1 MIT Yes Details →
3.17.2 16 Feb 2026 H1 M1 MIT Yes Details →
3.17.1 13 Feb 2026 H1 M1 MIT Yes Details →
3.17.0 11 Feb 2026 H1 M1 MIT Yes Details →
3.16.3 03 Feb 2026 H1 M1 MIT Yes Details →
3.16.3-canary.46c3f603 30 Jan 2026 H1 M1 MIT Yes Details →
3.16.2 26 Jan 2026 H1 M1 MIT Yes Details →
3.16.2-canary.2927949d 26 Jan 2026 H1 M1 — Yes Details →
3.16.2-canary.089a628c 17 Jan 2026 H1 M1 — Yes Details →
3.16.1 16 Jan 2026 H1 M1 — Yes Details →
3.16.1-canary.3e00cd75 15 Jan 2026 H1 M1 — Yes Details →
3.16.0 16 Dec 2025 H1 M1 — Yes Details →
3.15.4-canary.a3944878 16 Dec 2025 H1 M1 — Yes Details →
3.15.3 21 Oct 2025 H1 M1 — Yes Details →
3.15.3-canary.6000eb2f 14 Oct 2025 H1 M1 — Yes Details →
3.15.2 08 Oct 2025 H1 M1 — Yes Details →
3.15.2-canary.fb9eae11 03 Oct 2025 H1 M1 — Yes Details →
3.15.1 24 Sep 2025 H1 M1 — Yes Details →
3.15.1-canary.53a9bc24 24 Sep 2025 H1 M1 — Yes Details →
3.15.1-canary.288d757b 18 Sep 2025 H1 M1 — Yes Details →
3.15.0 16 Sep 2025 H1 M1 — Yes Details →
3.14.6-canary.e72247f7 09 Sep 2025 H1 M1 — Yes Details →
3.14.5 08 Sep 2025 H1 M1 — Yes Details →
3.14.5-canary.c091f1ba 08 Sep 2025 H1 M1 — Yes Details →
3.14.4 01 Sep 2025 H1 M1 — Yes Details →
3.14.4-canary.64ea4cdd 01 Sep 2025 H1 M1 — Yes Details →
3.14.4-canary.9642a1e5 27 Aug 2025 H1 M1 — Yes Details →

The newest 120 of 329 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2024 5
  • 2026 2

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 2 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for mysql2

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2024-21508: mysql2 Remote Code Execution (RCE) 9.8 critical 3.9.4 11 Apr 2024
CVE-2024-21511: MySQL2 for Node Arbitrary Code Injection 9.8 critical 3.9.7 23 Apr 2024
CVE-2024-21512: Prototype Pollution in mysql2 8.2 high 3.9.8 30 May 2024
MySQL2 Auth Plugin Downgrade Vulnerability: Plaintext Credential Exposure 8.2 high 3.22.0 01 Sep 2026
mysql2 cache poisoning vulnerability in npm/mysql2 6.5 medium 3.9.3 10 Apr 2024

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About mysql2

Is mysql2 safe to use?

Vulert records 7 vulnerabilities for mysql2 in npm: 2 critical, 2 high, 3 medium and 0 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is mysql2's Vulert package health score?

Vulert scores mysql2 79/100, which reads as in good shape. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of mysql2 affected?

No. 3.24.6, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does mysql2 have?

7 vulnerabilities are recorded for mysql2 in the npm ecosystem: 2 critical, 2 high, 3 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new mysql2 vulnerabilities disclosed?

2 vulnerabilities were recorded for mysql2 in the last 12 months, and the oldest entry in this database dates to 10 Apr 2024. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of mysql2 are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor mysql2 for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the mysql2 version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.