MariaDB vulnerabilities
7 known CVE vulnerabilities in MariaDB, translated and rated.
- CVE-2026-44172Critical
SQL injection vulnerability in MariaDB (versions 3.3.18 and 3.4.8) despite using mysql_real_escape_string() with big5 charset. Fixed in versions 3.3.19 and 3.4.9.
- CVE-2026-44170Critical
A vulnerability in MariaDB on Windows with the CONNECT engine installed and REST support enabled allows interpolation of the table HTTP attribute into the curl command line without proper sanitization. This enables the user to execute shell commands on the server.
- CVE-2026-48165High
A vulnerability in MariaDB server allows a high-privileged user to execute shell commands via the wsrep_sst_receive_address or wsrep_sst_donor global system variables. Affected versions range from 10.6.1 to before 10.6.27, 10.11.1 to before 10.11.18, 11.4.1 to before 11.4.12, 11.8.1 to before 11.8.8, and 12.3.1.
- CVE-2026-48163High
A vulnerability in MariaDB allows a malicious joiner node to execute arbitrary shell commands on the donor node during the SST (State Snapshot Transfer) process using the rsync method. The issue stems from insufficient validation of parameters sent by the joiner, which are interpolated into the command line on the donor side.
- CVE-2026-44173Medium
A vulnerability in MariaDB allows SELECT ... INTO OUTFILE and SELECT ... INTO DUMPFILE without the required FILE privilege when the FROM clause contains only subqueries. Affected versions include 10.6.1 to 10.6.26, 10.11.1 to 10.11.17, 11.4.1 to 11.4.11, 11.8.1 to 11.8.7, and 12.3.1.
- CVE-2026-44168High
A vulnerability in MariaDB allows a malicious joiner node to execute arbitrary shell commands on the donor node during the SST (Snapshot State Transfer) process using the mariabackup method. The issue is caused by insufficient validation of parameters sent by the joiner, which are interpolated into the command line on the donor side.
- CVE-2026-3494Medium
In MariaDB server up to version 11.8.5, when the server audit plugin is enabled with the server_audit_events variable configured with QUERY_DCL, QUERY_DDL, or QUERY_DML filtering, an authenticated database user can invoke a SQL statement prefixed with double-hyphen (--) or hash (#) style comments, which is not logged.

