Vulnerability Database · Debian · Package report

mariadb: vulnerability history, versions and safety

mariadb is a package in the Debian ecosystem. Vulert records 47 vulnerabilities for it across 58 releases, from Nov -0001 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
47 vulnerabilities recorded U47
i
31 with no fix published

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

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

Most recent disclosure 16 Oct 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on mariadb i

Updated on 23 Oct 2026

Careful: 31 of the 47 vulnerabilities Vulert records for this package have no fix yet. Plan around those, or apply the workaround listed for each. The rest have a fixed version to move to.

Long-term outlook: usable, but needs attention 47 vulnerabilities on record across 2026 years, 32 in the last year.

What to do: Plan around the 31 vulnerabilities with no published fix: each lists the affected range and any workaround that reduces exposure. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Vulnerabilities on record 47 over 2026 years · 32 in the last year i
  • Latest disclosure 16 Oct 2026 i
  • Highest CVSS 9.9 i
  • With no published fix 31 i

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 holds for mariadb, newest first, with the vulnerabilities that name it. A version with a count of zero has no recorded vulnerabilities; open a version to see the vulnerabilities it is exposed to.

i
Version Vulert vulnerabilities Fix published Details
1:11.8.9+ds-4 U13 No Details →
1:11.8.9+ds-3 U13 No Details →
1:11.8.9+ds-2 U13 No Details →
1:11.8.9+ds-1 U19 No Details →
1:11.8.8-1 U28 No Details →
1:11.8.6-6 U28 No Details →
1:11.8.6-5 U28 No Details →
1:11.8.6-4 U29 No Details →
1:11.8.6-3 U29 No Details →
1:11.8.6-2 U30 No Details →
1:11.8.6-1 U30 No Details →
1:11.8.5-4 U30 No Details →
1:11.8.5-3 U30 No Details →
1:11.8.5-3~exp3 U30 No Details →
1:11.8.5-3~exp2 U30 No Details →
1:11.8.5-3~exp1 U30 No Details →
1:11.8.5-2 U30 No Details →
1:11.8.5-1 U30 No Details →
1:11.8.3-1 U31 No Details →
1:11.8.2-1 U31 No Details →
1:11.8.1-5 U31 No Details →
1:11.8.1-4 U31 No Details →
1:11.8.1-3 U31 No Details →
1:11.8.1-2 U31 No Details →
1:11.8.1-1 U31 No Details →
1:11.4.5-2~exp1 U31 No Details →
1:11.4.5-1 U31 No Details →
1:11.4.4-3 U31 No Details →
1:11.4.4-2 U31 No Details →
1:11.4.4-1 U31 No Details →
1:11.4.3-1 U31 No Details →
1:11.4.2-4 U31 No Details →
1:11.4.2-3 U31 No Details →
1:11.4.2-2 U31 No Details →
1:11.4.2-1 U31 No Details →
1:10.11.19-0+deb12u1 U6 No Details →
1:10.11.18-0+deb12u1 U19 No Details →
1:10.11.14-0+deb12u2 U33 No Details →
1:10.11.14-0+deb12u1 U33 No Details →
1:10.11.13-0+deb12u1 U33 No Details →
1:10.11.11-0+deb12u1 U43 No Details →
1:10.11.9-0+deb12u1 U45 No Details →
1:10.11.8-1 U45 No Details →
1:10.11.7-4 U45 No Details →
1:10.11.7-3 U45 No Details →
1:10.11.7-2 U45 No Details →
1:10.11.7-1 U45 No Details →
1:10.11.6-2.1~exp1 U45 No Details →
1:10.11.6-2 U45 No Details →
1:10.11.6-1 U45 No Details →
1:10.11.6-0+deb12u1 U45 No Details →
1:10.11.5-3 U46 No Details →
1:10.11.5-2 U46 No Details →
1:10.11.5-1 U46 No Details →
1:10.11.4-1 U46 No Details →
1:10.11.4-1~deb12u1 U46 No Details →
1:10.11.3-2~exp1 U46 No Details →
1:10.11.3-1 U46 No Details →

Newest 58 of 58 versions on record. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 0 1
  • 2023 2
  • 2024 1
  • 2025 11
  • 2026 32

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

03 Vulnerabilities

Recorded vulnerabilities for mariadb

The 5 most severe of 47 vulnerabilities recorded for this package

Search all 47 in the database →

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 47 vulnerabilities for mariadb in Debian: 0 critical, 0 high, 0 medium and 0 low, plus 47 not yet rated. 31 of them have no published fix yet, so those are the ones to avoid or mitigate.

How many vulnerabilities does mariadb have?

47 vulnerabilities are recorded for mariadb in the Debian ecosystem: 0 critical, 0 high, 0 medium and 0 low, plus 47 not yet rated. 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?

32 vulnerabilities were recorded for mariadb in the last 12 months, and the oldest entry in this database dates to 30 Nov -0001. 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.