CVE-2026-92262: MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass.
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 Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
MariaDB serverto a version that resolves this vulnerability.Fixed in 10.6.28 - Upgrade
Upgrade
MariaDB serverto a version that resolves this vulnerability.Fixed in 10.11.19 - Upgrade
Upgrade
MariaDB serverto a version that resolves this vulnerability.Fixed in 11.4.13 - Upgrade
Upgrade
MariaDB serverto a version that resolves this vulnerability.Fixed in 11.8.9 - Upgrade
Upgrade
MariaDB serverto a version that resolves this vulnerability.Fixed in 12.3.3 - Upgrade
Upgrade
MariaDB serverto a version that resolves this vulnerability.Fixed in 13.0.2
Event History
Frequently Asked Questions
Which deployments are affected?
MariaDB Server versions from 10.6.1 through the fixed releases are affected. The fixed versions are 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.
What access does an attacker need?
The supplied vector indicates network reachability, low attack complexity, no user interaction, and low privileges required. Exploitation involves creating or using a table name with the #mysql50# prefix.
What is the practical impact of successful exploitation?
The bypass can permit access to files under legacy unencoded names. Reported outcomes include server crashes, data corruption, data exfiltration, and remote code execution.
How can exposure be reduced if an immediate upgrade is not possible?
The provided information identifies #mysql50# table names as the exploitation mechanism. Restrict low-privileged users from creating or using such table names until the server can be upgraded to a fixed release.