dbcve.org
MariaDBDatabase / datastore

CVE-2026-44171

HIGH · 7.8 CVSS v3.1 Published 2026-06-12
Fix available
A fix is available. Upgrade to 10.6.26 / 10.11.17 or later.
See remediation →
81/100
Remediation priority · High
No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Path traversal vulnerability in MariaDB's mbstream backup utility where the tool fails to validate paths containing '/../' sequences during archive extraction. A specially crafted archive can write files outside the intended target directory, enabling arbitrary file write operations.

MitigationUpgrade MariaDB to version 10.6.26, 10.11.17, 11.4.11, 11.8.7, or 12.3.2 or later to obtain the patch. If immediate upgrading is not feasible, restrict mbstream usage to trusted sources and ensure backup archives originate from verified, non-compromised systems.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
MariaDBDatabase / datastore
Affected:>= 10.6.1, < 10.6.26>= 10.11.1, < 10.11.17>= 11.4.1, < 11.4.11>= 11.8.1, < 11.8.7= 12.3.1

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed MariaDB version
    Run 'mariadb --version' or 'mysql --version' to obtain the server version number
    Affected if The version falls within these ranges: 10.6.1 to 10.6.25, 10.11.1 to 10.11.16, 11.4.1 to 11.4.10, 11.8.1 to 11.8.6, or 12.3.1
  2. Locate mbstream utility
    Run 'which mbstream' or search for the binary in MariaDB installation directories such as /usr/bin/, /usr/local/bin/, or <MariaDB_prefix>/bin/
    Affected if The mbstream binary is present on the system
  3. Check for backup extraction scripts
    Inspect any scripts or cron jobs that invoke mbstream with the -x flag (extraction mode), look for commands like 'mbstream -x < archive' in /etc/cron.d/, /opt/, or database backup directories
    Affected if mbstream is configured to extract archives from backup files
  4. Audit recent mbstream extraction activity
    Review system logs, database audit logs, or backup job logs for recent mbstream extraction operations; check file access timestamps on backup archives in backup storage locations
    Affected if mbstream has been recently used to extract backup archives

You are affected if your MariaDB version is within the vulnerable ranges AND the mbstream utility is present and used to extract backup archives, particularly from sources that may not be fully trusted.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 10.6.26 / 10.11.17 / 11.4.11 or later
Fixed in 10.6.2610.11.1711.4.11
Interim mitigation

Upgrade MariaDB to version 10.6.26, 10.11.17, 11.4.11, 11.8.7, or 12.3.2 or later to obtain the patch. If immediate upgrading is not feasible, restrict mbstream usage to trusted sources and ensure backup archives originate from verified, non-compromised systems.

Recommended fix High confidence

10.6.26, 10.11.17, 11.4.11, 11.8.7, or 12.3.2 (depending on your current major version branch)

  1. Identify the current MariaDB version by running 'mysql --version' or 'mariadb --version'
  2. Determine which major version branch you are on (10.6.x, 10.11.x, 11.4.x, 11.8.x, or 12.3.x)
  3. Stop the MariaDB service using 'systemctl stop mariadb' or 'service mysql stop'
  4. Perform a full backup of all databases using mysqldump or mariadb-backup
  5. Upgrade MariaDB to the appropriate fixed version: For 10.6.x upgrade to 10.6.26, for 10.11.x upgrade to 10.11.17, for 11.4.x upgrade to 11.4.11, for 11.8.x upgrade to 11.8.7, or for 12.3.x upgrade to 12.3.2
  6. Start the MariaDB service using 'systemctl start mariadb' or 'service mysql start'
  7. Verify the upgrade by running 'mysql --version' or 'mariadb --version' to confirm the new version is installed
Caveat Minor version upgrades within the same major release line typically have minimal breaking changes; always review the release notes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MariaDB Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44171 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44171 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data