All vulnerabilities
CVE-2026-92262GHSA-65jj-h265-3m7h

server: MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass.

MariaDB serverDatabases
Open in ThreatlineRecord JSON
CVSS
9.9Critical
ExploitationNo known exploitationNot in CISA KEV, which does not prove it is unexploitedCISA KEV
Exploit odds (EPSS)0.73%Chance of exploitation activity in the next 30 days, higher than 53% of CVEs. Scored 23 Oct 2026FIRST EPSS
Fixed in10.6.28Also 10.11.19, 11.4.13 and 3 moreGitHub
Published16 Oct 2026Updated 21 Oct 2026CVE List

What fixes it

A fixed version on one release line is not the upgrade target for every line. Check your exact version and any vendor backports.

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.

Text from CVE List

Affected versions 7

  • serveraffected: >= 10.6.1, < 10.6.28CVE List
  • serveraffected: >= 10.11.1, < 10.11.19CVE List
  • serveraffected: >= 11.4.1, < 11.4.13CVE List
  • serveraffected: >= 11.8.1, < 11.8.9CVE List
  • serveraffected: >= 12.3.1, < 12.3.3CVE List
  • serveraffected: >= 13.0.1, < 13.0.2CVE List
  • server10.6.1-10.6.27, 10.11.1-10.11.18, 11.4.1-11.4.12, 11.8.1-11.8.8, 12.3.1-12.3.2, 13.0.1GitHub

References 10