Description
MariaDB server is a community developed fork of MySQL server. From 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, the #mysql50# bypass prefix is affected because it allows the #mysql50# prefix to bypass normal table-name filesystem encoding. An attacker can trigger the issue with a table name using the #mysql50# prefix, then use a #mysql50# table name to access files under their legacy unencoded name and cause crashes, data corruption, data exfiltration, or remote code execution. This issue is fixed in versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.
Affected products
mariadb: mariadb
References10
- github.com/MariaDB/server/security/advisories/GHSA-65jj-h265-3m… Vendor Advisory
- github.com/MariaDB/server/commit/574ba66b2d6c5d71db83d416677876… Patch
- github.com/MariaDB/server/commit/f277eefa424850a8cba5c237140604… Patch
- github.com/MariaDB/server/releases/tag/mariadb-10.11.19 Release Notes
- github.com/MariaDB/server/releases/tag/mariadb-10.6.28 Release Notes
- github.com/MariaDB/server/releases/tag/mariadb-11.4.13 Release Notes
- github.com/MariaDB/server/releases/tag/mariadb-11.8.9 Release Notes
- github.com/MariaDB/server/releases/tag/mariadb-12.3.3 Release Notes
- github.com/MariaDB/server/releases/tag/mariadb-13.0.2 Release Notes
- jira.mariadb.org/browse/MDEV-40362 Issue Tracking
Metrics
- CVSS 3.1
-
9.9
CRITICAL
Score source: CNA
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H - EPSS — exploit probability
- 1% percentile: 74 · as of 10 November 2026
- CWE
- CWE-706
Could this be exploited in your environment?
A patch closes the known hole. A penetration test shows what an attacker can still reach — with proof.