CVE-2026-44171·MariaDB vulnerability
MariaDB server is a community developed fork of MySQL server. From versions 10.6.1 to before 10.6.26, 10.11.1 to before 10.11.17, 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1, mbstream did not check for /../ in the path when unpacking the archive. A proper backup can never contain such paths, but a specially crafted archive could have caused mbstream to create files outside of the target-dir path. This issue has been patched in versions 10.6.26, 10.11.17, 11.4.11, 11.8.7, and 12.3.2.
- Severity
- medium
- Software
- MariaDB
- Fixed in
- 11.8.7
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.17% — higher than 7% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 11.8.1
Until: 11.8.7
Fixed in: 11.8.7
How to fix this CVE
Update MariaDB to version 11.8.7 or later to patch a path traversal vulnerability in the mbstream backup restoration utility. The vulnerability allows specially crafted backup archives to extract files outside the intended target directory. Apply the update immediately if you use mbstream for backup operations.
sudo dnf update mariadb-serverDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check MariaDB version by running: mysql --version or mariadb --version
- Step 2: Query the server version with: SELECT @@version; from the MariaDB command line
- Step 3: Review mbstream usage in your backup logs: grep -r 'mbstream' /var/log/ to identify if the affected component is in use
- Step 4: Verify the patch by re-running mysql --version after update and confirming version is 11.8.7 or higher
FAQ
What is CVE-2026-44171?
This vulnerability is a path traversal flaw in MariaDB's mbstream backup restoration tool that fails to validate archive paths containing directory traversal sequences (/../). An attacker could craft a malicious backup archive to write files outside the specified target directory.
Is CVE-2026-44171 being actively exploited?
No, this vulnerability is not listed in CISA's Known Exploited Vulnerabilities (KEV) catalog and no public exploits are currently available.
What versions of MariaDB are affected by CVE-2026-44171?
MariaDB 11.8.1 through 11.8.6 are vulnerable; version 11.8.7 and later contain the fix. Earlier major versions 10.6.1–10.6.25, 10.11.1–10.11.16, and 11.4.1–11.4.10 are also affected with their respective patched versions available.
How do I check if my server is vulnerable to CVE-2026-44171?
Run: mariadb --version or SELECT @@version; If the version is between 11.8.1 and 11.8.6, your installation is vulnerable and requires immediate patching.
Does Defensia detect CVE-2026-44171?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If MariaDB is installed on a monitored server, CVE-2026-44171 will appear in your dashboard with remediation steps.
Related MariaDB CVEs
References
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-44171. Free for 1 server.
Get started free