Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2026-44171: MariaDB server is a community developed fork of MySQL server

29
Routine
MEDIUM 6.3WATCHLISTUPGRADE

CVE-2026-44171 is a medium-severity flaw (CVSS 6.3) affecting mariadb. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 v

Why this priority

  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score6.3 (Medium)
Attack vectorLocal
Attack complexityHigh
Privileges neededHigh
User interactionRequired
EPSS exploit chance0.2% (top 92%)
CISA exploited listNo
WeaknessCWE-22
Published2026-06-12
Last modified2026-10-26
Publisher (CNA): GitHub, Inc. · Vendor: mariadb

Share: LinkedIn · X · Reddit

Last updated 2026-10-26 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

mariadb mariadb UPGRADE
Affected: >= 10.6.1 and < 10.6.26 · >= 10.11.1 and < 10.11.17 · >= 11.4.1 and < 11.4.11 · >= 11.8.1 and < 11.8.7 · 12.3.1
Fixed in: 10.6.26, 10.11.17, 11.4.11, 11.8.7
Safe to downgrade to: a release before 10.6.1
1. Check installed version
apt-cache policy mariadb || rpm -q mariadb || mariadb --version
2. UPGRADE to 10.6.26 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade mariadb
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade mariadb
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
3. If no update is available yet, DOWNGRADE to a release before 10.6.1 (Debian / Ubuntu)
apt-cache madison mariadb sudo apt install mariadb=<VERSION_BEFORE_10.6.1> sudo apt-mark hold mariadb
3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list mariadb sudo dnf downgrade mariadb-<VERSION_BEFORE_10.6.1> sudo dnf versionlock add mariadb
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-44171?

mariadb: upgrade to 10.6.26, 10.11.17, 11.4.11, 11.8.7. Exact commands for each OS are on this page.

Is CVE-2026-44171 being exploited?

CVE-2026-44171 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-44171 affect?

CVE-2026-44171 affects mariadb. Severity is medium (CVSS 6.3). 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 whe

How urgent is CVE-2026-44171?

Priority 29/100. On your watchlist

Software pages

MySQL vulnerabilities · MariaDB vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.