dbcve.org
MariaDBDatabase / datastore

CVE-2026-44168

HIGH · 8.0 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 →
86/100
Remediation priority · High
Remotely reachable Zero-click

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, during the SST the donor node is interpolating parameters that the joiner sent into the command line. Not all parameters were properly validated which could allow a malicious joiner to execute arbitrary shell commands on the donor side via the mariabackup SST method. 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

During MariaDB's State Snapshot Transfer (SST) process using the mariabackup method, the donor node improperly interpolates parameters received from the joiner into a shell command line without proper validation. This allows a malicious or compromised joiner node to inject and execute arbitrary shell commands on the donor node, resulting in remote code execution.

MitigationUpgrade MariaDB to version 10.6.26, 10.11.17, 11.4.11, 11.8.7, 12.3.2 or later. If immediate patching is not possible, restrict network access between cluster nodes and monitor for unusual SST activity.

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
Network
Complexity
High
Privileges
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/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. Check installed MariaDB version
    Run 'mysql --version' or 'mariadb --version' to get the exact version number
    Affected if Version falls within >= 10.6.1, < 10.6.26 OR >= 10.11.1, < 10.11.17 OR >= 11.4.1, < 11.4.11 OR >= 11.8.1, < 11.8.7 OR equals 12.3.1
  2. Verify Galera cluster is in use
    Check configuration files (my.cnf or my.ini) for 'wsrep_cluster' settings, or run 'SHOW STATUS LIKE 'wsrep_cluster_size';' in mysql client
    Affected if The MariaDB server is configured as part of a Galera cluster
  3. Identify SST method configured
    Check Galera SST configuration in my.cnf for 'wsrep_sst_method' setting. Common locations: [mysqld] or [galera] sections. Run 'grep -r wsrep_sst_method /etc/mysql/' if needed
    Affected if wsrep_sst_method is set to 'mariabackup' (vulnerability applies only to this method; xtrabackup, rsync, and other methods are not affected)
  4. Confirm mariabackup binary availability
    Check if mariabackup binary exists on the system: 'which mariabackup' or 'ls -la /usr/bin/mariabackup'
    Affected if mariabackup is installed and available on the donor node

You are affected if your MariaDB version is in the affected range AND you are using Galera cluster with mariabackup as the SST method.

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, 12.3.2 or later. If immediate patching is not possible, restrict network access between cluster nodes and monitor for unusual SST activity.

Recommended fix High confidence

Upgrade to 10.6.26 (if on 10.6.x), 10.11.17 (if on 10.11.x), 11.4.11 (if on 11.4.x), 11.8.7 (if on 11.8.x), or 12.3.2 (if on 12.x)

  1. 1. Check current MariaDB version: `mysql -V` or `mariadb --version`
  2. 2. Identify which version branch you are currently on (10.6.x, 10.11.x, 11.4.x, or 11.8.x)
  3. 3. Create a full backup of all databases before upgrading: `mysqldump --all-databases > full_backup.sql` (or use mariabackup for physical backup)
  4. 4. For RHEL/CentOS/Fedora: Run `sudo yum update mariadb-server` or `sudo dnf update mariadb-server`
  5. 5. For Debian/Ubuntu: Run `sudo apt update && sudo apt install mariadb-server`
  6. 6. After package installation, restart the MariaDB service: `sudo systemctl restart mariadb`
  7. 7. Verify the upgrade was successful by checking version: `mysql -V`
  8. 8. Test that the MariaDB service is running properly: `sudo systemctl status mariadb`
Caveat MariaDB minor version upgrades are generally low-risk but always test in staging first; review release notes for any behavior changes in your version branch

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

Fix this in MariaDB Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44168 — 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-44168 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