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.
Published: 2026-10-16
Score: 9.9 Critical
EPSS: 1.5% Low
KEV: No
Impact: Remote Code Execution
Action: Immediate Patch
AI Analysis

Impact

The vulnerability arises from a historical #mysql50# tablename encoding bypass that allows a table name prefixed with #mysql50# to access files under their legacy unencoded name. This bypass effectively removes normal filesystem encoding checks, enabling the attacker to trigger crashes, corrupt data, exfiltrate sensitive information, or ultimately execute arbitrary code. The weakness is a failure of proper authorization control, corresponding to CWE-706 and CWE-73.

Affected Systems

Affected systems are MariaDB Server installations. Version ranges 10.6.1 through 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2 are impacted. The issue is mitigated in the releases 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, and later major releases.

Risk and Exploitability

The CVSS score of 9.9 signals an extremely high severity. Although EPSS score of 0.00725 (less than 1%) indicates a very low but nonzero exploitation probability, the lack of a public exploit and its absence from CISA KEV suggests no widespread exploitation yet, but the high severity and remote nature of the flaw — an attacker who can create a table with the #mysql50# prefix can access arbitrary files and may gain code execution — render it a critical threat. Permission to create tables is generally restricted to database administrators; thus the vulnerability is primarily a privilege‑escalation or misuse vector for users with elevated DB rights.

Generated by OpenCVE AI on October 24, 2026 at 02:07 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade MariaDB to a patched release that removes the #mysql50# prefix bypass (10.6.28 or newer, 10.11.19 or newer, 11.4.13 or newer, 11.8.9 or newer, 12.3.3 or newer, 13.0.2 or newer).
  • If upgrading immediately is not possible, delete or rename any tables that use the #mysql50# prefix to eliminate the attack surface.
  • Restrict the CREATE TABLE privilege to trusted administrators and consider disabling the creation of tables with the #mysql50# prefix as a temporary control.

Generated by OpenCVE AI on October 24, 2026 at 02:07 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Sat, 24 Oct 2026 00:30:00 +0000

Type Values Removed Values Added
Weaknesses CWE-73
References
Metrics threat_severity

None

threat_severity

Important


Fri, 23 Oct 2026 11:00:00 +0000

Type Values Removed Values Added
First Time appeared Mariadb server
Vendors & Products Mariadb server

Wed, 21 Oct 2026 03:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 20 Oct 2026 15:45:00 +0000

Type Values Removed Values Added
First Time appeared Mariadb
Mariadb mariadb
CPEs cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
cpe:2.3:a:mariadb:mariadb:13.0.1:*:*:*:*:*:*:*
Vendors & Products Mariadb
Mariadb mariadb

Fri, 16 Oct 2026 16:45:00 +0000

Type Values Removed Values Added
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.
Title MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass.
Weaknesses CWE-706
References
Metrics cvssV3_1

{'score': 9.9, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H'}


cve-icon MITRE

Status: PUBLISHED

Assigner: GitHub_M

Published:

Updated: 2026-10-21T02:28:14.389Z

Reserved: 2026-09-15T22:16:18.049Z

Link: CVE-2026-92262

cve-icon Vulnrichment

Updated: 2026-10-21T02:28:10.327Z

cve-icon NVD

Status : Analyzed

Published: 2026-10-16T17:17:52.710

Modified: 2026-10-21T03:17:20.003

Link: CVE-2026-92262

cve-icon Redhat

Severity : Important

Publid Date: 2026-10-16T16:25:46Z

Links: CVE-2026-92262 - Bugzilla

cve-icon OpenCVE Enrichment

Updated: 2026-10-24T02:15:17Z

Weaknesses
  • CWE-706

    Use of Incorrectly-Resolved Name or Reference

  • CWE-73

    External Control of File Name or Path