VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

mariadb: vulnerability history, versions and safety

mariadb is a package in the npm ecosystem. Vulert records 8 vulnerabilities for it across 58 releases, from Jul 2018 to Oct 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H5 M3
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
7 in the last 12 months

Most recent disclosure 08 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all mariadb vulnerabilities

Vulert verdict on mariadb 3.5.4 i

Updated on 23 Oct 2026

Careful: 3.5.4 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 3.5.4 — affected i
  • Vulnerabilities on record 8 over 8 years · 7 in the last year i
  • Latest disclosure 08 Oct 2026 i
  • Highest CVSS 8.1 i
  • With no published fix 1 i
  • Depended on by 354 packages i
  • Stars 413 i
  • OpenSSF scorecard 3/10 i
  • Last release 1 month ago i
  • Licence LGPL-2.1-or-later 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 mariadb, 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.3.4 01 Sep 2026 H1 M1 LGPL-2.1-or-later No Details →
3.4.7 01 Sep 2026 H1 M1 LGPL-2.1-or-later No Details →
3.5.4 01 Sep 2026 H1 LGPL-2.1-or-later No Details →
3.2.5 01 Sep 2026 H1 LGPL-2.1-or-later No Details →
3.5.3 09 Jun 2026 H1 M1 LGPL-2.1-or-later No Details →
3.5.2 06 Mar 2026 H1 M1 LGPL-2.1-or-later No Details →
3.5.1 18 Feb 2026 H1 M1 LGPL-2.1-or-later No Details →
3.4.5 23 Jul 2025 H1 M1 LGPL-2.1-or-later No Details →
3.4.4 03 Jul 2025 H1 M1 LGPL-2.1-or-later No Details →
3.4.3 02 Jul 2025 H1 M1 LGPL-2.1-or-later No Details →
3.4.2 25 Apr 2025 H1 M1 LGPL-2.1-or-later No Details →
3.4.1 02 Apr 2025 H1 M1 LGPL-2.1-or-later No Details →
3.4.0 24 Oct 2024 H1 M1 LGPL-2.1-or-later No Details →
3.3.2 18 Sep 2024 H1 M1 LGPL-2.1-or-later No Details →
3.3.1 05 Jun 2024 H1 M1 LGPL-2.1-or-later No Details →
3.3.0 21 Mar 2024 H1 M1 LGPL-2.1-or-later No Details →
3.2.3 19 Dec 2023 H5 M2 LGPL-2.1-or-later No Details →
3.2.2 16 Oct 2023 H5 M2 LGPL-2.1-or-later No Details →
3.2.1 14 Sep 2023 H5 M2 LGPL-2.1-or-later No Details →
3.2.0 19 Jun 2023 H5 M2 LGPL-2.1-or-later No Details →
3.1.2 03 May 2023 H4 M2 LGPL-2.1-or-later No Details →
3.1.1 17 Mar 2023 H4 M2 LGPL-2.1-or-later No Details →
3.1.0 15 Feb 2023 H4 M2 LGPL-2.1-or-later No Details →
3.0.2 27 Oct 2022 H4 M2 LGPL-2.1-or-later No Details →
3.0.1 26 Jul 2022 H4 M2 LGPL-2.1-or-later No Details →
3.0.0 01 Mar 2022 H4 M2 LGPL-2.1-or-later No Details →
2.5.6 17 Feb 2022 H4 M2 LGPL-2.1-or-later No Details →
3.0.0-rc.0 20 Oct 2021 H4 M2 LGPL-2.1-or-later No Details →
2.5.5 20 Oct 2021 H4 M2 LGPL-2.1-or-later No Details →
3.0.0-beta 21 Jun 2021 H4 M2 LGPL-2.1-or-later No Details →
2.5.4 21 Jun 2021 H4 M2 LGPL-2.1-or-later No Details →
2.5.3 16 Feb 2021 H4 M2 LGPL-2.1-or-later No Details →
2.5.2 04 Dec 2020 H4 M2 LGPL-2.1-or-later No Details →
2.5.1 23 Oct 2020 H4 M2 LGPL-2.1-or-later No Details →
2.5.0 15 Oct 2020 H4 M2 LGPL-2.1-or-later No Details →
2.4.2 23 Jul 2020 H4 M2 LGPL-2.1-or-later No Details →
2.4.1 01 Jul 2020 H4 M2 LGPL-2.1-or-later No Details →
2.4.0 25 May 2020 H4 M2 LGPL-2.1-or-later No Details →
2.3.1 20 Mar 2020 H4 M2 LGPL-2.1-or-later No Details →
2.3.0 20 Mar 2020 H4 M2 LGPL-2.1-or-later No Details →
2.2.0 04 Feb 2020 H4 M2 LGPL-2.1-or-later No Details →
2.1.5 07 Jan 2020 H4 M2 LGPL-2.1-or-later No Details →
2.1.4 02 Dec 2019 H4 M2 LGPL-2.1+ No Details →
2.1.3 14 Nov 2019 H4 M2 LGPL-2.1+ No Details →
2.1.2 17 Oct 2019 H4 M2 LGPL-2.1+ No Details →
2.1.1 06 Sep 2019 H4 M2 LGPL-2.1+ No Details →
2.1.0 11 Jul 2019 H4 M2 LGPL-2.1+ No Details →
2.0.5 10 May 2019 H4 M2 LGPL-2.1+ No Details →
2.0.4 07 May 2019 H4 M2 LGPL-2.1+ No Details →
2.0.3 31 Jan 2019 H4 M2 LGPL-2.1+ No Details →
2.0.2-rc 11 Dec 2018 H4 M2 LGPL-2.1+ No Details →
2.0.1-beta 15 Nov 2018 H4 M2 LGPL-2.1+ No Details →
2.0.0-alpha 20 Sep 2018 H4 M2 LGPL-2.1+ No Details →
0.7.0 17 Jul 2018 H4 M2 LGPL-2.1+ No Details →
0.0.2-security 02 Aug 2017 H4 M2 LGPL-2.1-or-later No Details →
1.0.2 01 Aug 2017 H4 M2 ISC No Details →
1.0.1 01 Aug 2017 H4 M2 ISC No Details →
0.0.1-security 01 Aug 2017 H4 M2 LGPL-2.1-or-later No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2026 7

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

03 Vulnerabilities

Recorded vulnerabilities for mariadb

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2026-107384: MariaDB Connector/Node.js SQL Injection via Object Keys in SET Expansion 8.1 high 3.2.5 08 Oct 2026
CVE-2017-16046: Hijacked Environment Variables in mariadb 7.5 high No fix published 18 Jul 2018
CVE-2026-55215: MariaDB Connector Password Leak in SSL/TLS Connections 7.5 high 3.2.4 28 Aug 2026
CVE-2026-107383: MariaDB Connector/Node.js Exposes Uninitialized Memory Through Malformed GeoJSON Parameters 7.5 high 3.2.5 08 Oct 2026
CVE-2026-107385: SQL Injection Vulnerability in MariaDB Connector/Node.js Due to Improper Escaping 7.4 high 3.2.5 08 Oct 2026

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 mariadb

Is mariadb safe to use?

Vulert records 8 vulnerabilities for mariadb in npm: 0 critical, 5 high, 3 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is mariadb's Vulert package health score?

Vulert scores mariadb 60/100, which reads as usable, but worth attention. 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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of mariadb affected?

Yes. 3.5.4, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of mariadb should I use?

3.5.4 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 mariadb have?

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

7 vulnerabilities were recorded for mariadb in the last 12 months, and the oldest entry in this database dates to 18 Jul 2018. 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 mariadb 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 mariadb for upcoming vulnerabilities?

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