VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mysql: vulnerability history, versions and safety

mysql is a package in the npm ecosystem. Vulert records 3 vulnerabilities for it across 58 releases, from May 2019 to May 2022. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
3 vulnerabilities recorded M3
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mysql vulnerabilities

Vulert verdict on mysql 2.18.1 i

Updated on 22 Oct 2026

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

Package health score 71/100
  • Security Minor issues
  • Maintenance Slowing
  • Popularity Key ecosystem project
  • Community Quiet

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

  • Current release 2.18.1 — unaffected i
  • Vulnerabilities on record 3 over 3 years · 0 in the last year i
  • Latest disclosure 24 May 2022 i
  • Highest CVSS 5.5 i
  • With no published fix 0 i
  • Depended on by 8,664 packages i
  • Stars 18,610 i
  • OpenSSF scorecard 2/10 i
  • Last release 80 months ago i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 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 mysql, 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
2.18.1 23 Jan 2020 none MIT — Details →
2.18.0 21 Jan 2020 none MIT — Details →
2.17.1 18 Apr 2019 M1 MIT Yes Details →
2.17.0 18 Apr 2019 none MIT — Details →
2.16.0 18 Jul 2018 none MIT — Details →
2.15.0 05 Oct 2017 none MIT — Details →
2.14.1 01 Aug 2017 none MIT — Details →
2.14.0 26 Jul 2017 none MIT — Details →
2.13.0 24 Jan 2017 M1 MIT Yes Details →
2.12.0 03 Nov 2016 M1 MIT Yes Details →
2.11.1 08 Jun 2016 M1 MIT Yes Details →
2.11.0 06 Jun 2016 M1 MIT Yes Details →
2.10.2 13 Jan 2016 M1 MIT Yes Details →
2.10.1 11 Jan 2016 M1 MIT Yes Details →
2.10.0 15 Dec 2015 M1 MIT Yes Details →
2.9.0 19 Aug 2015 M1 MIT Yes Details →
2.8.0 14 Jul 2015 M1 MIT Yes Details →
2.7.0 28 May 2015 M1 MIT Yes Details →
2.6.2 15 Apr 2015 M1 MIT Yes Details →
2.6.1 27 Mar 2015 M1 MIT Yes Details →
2.6.0 25 Mar 2015 M1 MIT Yes Details →
2.5.5 24 Feb 2015 M1 MIT Yes Details →
2.5.4 17 Dec 2014 M1 MIT Yes Details →
2.5.3 06 Nov 2014 M1 MIT Yes Details →
2.5.2 11 Oct 2014 M1 MIT Yes Details →
2.5.1 22 Sep 2014 M1 MIT Yes Details →
2.5.0 07 Sep 2014 M1 MIT Yes Details →
2.4.3 25 Aug 2014 M1 MIT Yes Details →
2.4.2 04 Aug 2014 M1 MIT Yes Details →
2.4.1 17 Jul 2014 M1 MIT Yes Details →
2.4.0 13 Jul 2014 M1 MIT Yes Details →
2.3.2 29 May 2014 M1 MIT Yes Details →
2.3.1 27 May 2014 M1 MIT Yes Details →
2.3.0 16 May 2014 M1 MIT Yes Details →
2.2.0 27 Apr 2014 M1 MIT Yes Details →
2.1.1 14 Mar 2014 M1 MIT Yes Details →
2.1.0 19 Feb 2014 M1 MIT Yes Details →
2.0.1 17 Jan 2014 M1 MIT Yes Details →
2.0.0 09 Jan 2014 M1 MIT Yes Details →
2.0.0-rc2 06 Dec 2013 M1 MIT Yes Details →
2.0.0-rc1 30 Nov 2013 M1 MIT Yes Details →
2.0.0-alpha9 28 Aug 2013 M1 MIT Yes Details →
2.0.0-alpha8 30 Apr 2013 M1 MIT Yes Details →
2.0.0-alpha7 03 Feb 2013 M1 MIT Yes Details →
2.0.0-alpha6 31 Jan 2013 M1 MIT Yes Details →
2.0.0-alpha5 03 Dec 2012 M1 MIT Yes Details →
2.0.0-alpha4 03 Nov 2012 M1 MIT Yes Details →
2.0.0-alpha3 25 Jun 2012 M1 MIT Yes Details →
2.0.0-alpha2 31 May 2012 M1 MIT Yes Details →
2.0.0-alpha 15 May 2012 M1 MIT Yes Details →
0.9.6 11 May 2012 M1 MIT Yes Details →
0.9.5 26 Nov 2011 M1 MIT Yes Details →
0.9.4 31 Aug 2011 M1 MIT Yes Details →
0.9.3 22 Aug 2011 M1 MIT Yes Details →
0.9.2 07 Aug 2011 M1 MIT Yes Details →
0.9.1 20 Feb 2011 M1 MIT Yes Details →
0.1.0 03 Jan 2011 M1 MIT Yes Details →
0.2.0 03 Jan 2011 M1 MIT Yes Details →
0.3.0 03 Jan 2011 M1 MIT Yes Details →
0.4.0 03 Jan 2011 M1 MIT Yes Details →
0.5.0 03 Jan 2011 M1 MIT Yes Details →
0.6.0 03 Jan 2011 M1 MIT Yes Details →
0.7.0 03 Jan 2011 M1 MIT Yes Details →
0.8.0 03 Jan 2011 M1 MIT Yes Details →
0.9.0 03 Jan 2011 M1 MIT Yes Details →

All 65 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2019 1
  • 2020 1
  • 2022 1

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

03 Vulnerabilities

Recorded vulnerabilities for mysql

The 3 most severe of 3 vulnerabilities recorded for this package

Search all 3 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2019-14939: MySQL for Node.js Unsafe Options 5.5 medium 2.18.0 24 May 2022
Vulnerability in mysql Node.JS Module: Remote Memory Exposure N/A medium 2.14.0 23 May 2019
CVE-2015-9244: SQL Injection in mysql N/A medium 2.0.0-alpha8 01 Sep 2020

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173

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 mysql

Is mysql safe to use?

Vulert records 3 vulnerabilities for mysql in npm: 0 critical, 0 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 mysql's Vulert package health score?

Vulert scores mysql 71/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 mysql affected?

No. 2.18.1, 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.

Which version of mysql should I use?

2.18.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does mysql have?

3 vulnerabilities are recorded for mysql in the npm ecosystem: 0 critical, 0 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 mysql vulnerabilities disclosed?

0 vulnerabilities were recorded for mysql in the last 12 months, and the oldest entry in this database dates to 23 May 2019. 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 mysql 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 mysql for upcoming vulnerabilities?

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