CVE-2026-44168·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, 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.
- Severity
- high
- Software
- MariaDB
- Fixed in
- 11.8.7
- Published
- 2026-06-12
Affected versions
From: 11.8.1
Until: 11.8.7
Fixed in: 11.8.7
How to fix this CVE
MariaDB versions 11.8.1 through 11.8.6 contain a critical vulnerability in the SST (State Snapshot Transfer) mechanism where parameter validation is insufficient, allowing malicious cluster nodes to execute arbitrary shell commands on the donor node. Upgrade to MariaDB 11.8.7 or later immediately, particularly if your deployment uses mariabackup for cluster replication. After patching, restart the MariaDB service and verify cluster synchronization.
sudo dnf update mariadb-serverDefensia detects this vulnerability
How to check if you are affected
- Step 1: Check installed MariaDB version by running `mariadb --version` or connecting to the database and executing `SELECT VERSION();`
- Step 2: Verify if SST/mariabackup is configured in `/etc/mysql/conf.d/` or `/etc/my.cnf.d/` by searching for `wsrep_sst_method` configuration parameter
- Step 3: Review MariaDB error logs at `/var/log/mysql/error.log` or `/var/log/mariadb/mariadb.log` for suspicious SST donor/joiner communications or shell command injection attempts
- Step 4: After upgrading, confirm the new version is active with `mariadb --version` and restart the service with `sudo systemctl restart mariadb`, then check cluster status with `SHOW STATUS LIKE 'wsrep%';`
FAQ
What is CVE-2026-44168?
CVE-2026-44168 is a command injection vulnerability in MariaDB's SST (State Snapshot Transfer) mechanism where insufficient parameter validation in the mariabackup method allows a malicious cluster node to inject and execute arbitrary shell commands on the donor node with database privileges.
Is CVE-2026-44168 being actively exploited?
No, this vulnerability is not listed on the CISA KEV catalog and no public exploits are currently available, but the high CVSS score (8.0) warrants prompt patching due to the severity of potential impact if exploited.
What versions of MariaDB are affected by CVE-2026-44168?
Affected versions include 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, and 12.3.1. For the 11.8 branch specifically, versions 11.8.1 through 11.8.6 are vulnerable.
How do I check if my server is vulnerable to CVE-2026-44168?
Run `mariadb --version` and cross-reference against the affected version ranges. Additionally, check if `wsrep_sst_method=mariabackup` is configured in your MariaDB configuration files, as this indicates the vulnerable SST method is in use.
Does Defensia detect CVE-2026-44168?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If MariaDB is installed on a monitored server, CVE-2026-44168 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-44168. Free for 1 server.
Get started free