Skip to main content
Vulnerability Database/CVE-2026-92262

CVE-2026-92262: MariaDB Server RCE Vulnerability

CVE-2026-92262 is a remote code execution vulnerability in MariaDB Server caused by the #mysql50# prefix bypass flaw. This post covers the technical details, affected versions, and mitigation strategies.

Published:

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

CVE-2026-92262 Overview

MariaDB server contains a filesystem name-encoding bypass that allows the #mysql50# table-name prefix to circumvent normal filesystem encoding routines. An authenticated attacker can craft a table name using the #mysql50# prefix to reference files under their legacy unencoded names on disk. Exploitation can lead to server crashes, data corruption, data exfiltration, or remote code execution. The flaw affects MariaDB releases from 10.6.1 up to the fixed versions and is tracked internally as MDEV-40362. MariaDB has issued patches in versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.

Critical Impact

An authenticated attacker with low privileges can achieve remote code execution and bypass MariaDB's filesystem name encoding across a wide range of production database deployments.

Affected Products

  • MariaDB server versions 10.6.1 through 10.6.27
  • MariaDB server versions 10.11.0 through 10.11.18, 11.4.0 through 11.4.12, 11.8.0 through 11.8.8
  • MariaDB server versions 12.3.0 through 12.3.2 and 13.0.0 through 13.0.1

Discovery Timeline

  • 2026-10-16 - CVE-2026-92262 published to NVD
  • 2026-10-21 - Last updated in NVD database

Technical Details for CVE-2026-92262

Vulnerability Analysis

The vulnerability stems from inconsistent handling of the #mysql50# identifier prefix within MariaDB's table-name-to-filename conversion logic. MariaDB historically used this prefix to maintain backward compatibility with MySQL 5.0 table names that did not use the modern filename encoding scheme. The server fails to properly validate or normalize names carrying this prefix before they reach disk operations and the table cache.

An attacker who can create or reference a table name beginning with #mysql50# can cause the server to resolve the name to an unencoded on-disk path. This behavior is classified under [CWE-706: Use of Incorrectly-Resolved Name or Reference]. The mismatch between in-memory table cache entries and the on-disk representation enables arbitrary file access within the data directory and corruption of partition metadata.

Root Cause

The root cause is a missing prefix check in functions that translate table identifiers to filesystem paths, including partition name translation in sql/ha_partition.cc and DDL log cleanup in sql/ddl_log.cc. The code called tablename_to_filename() without first rejecting names that carried the legacy prefix, allowing those names to bypass encoding and collide with other objects on disk.

Attack Vector

Exploitation requires network access to the MariaDB service and credentials with privileges to create or alter tables and partitions. The attacker issues DDL statements that embed #mysql50# in the table or partition name. Subsequent operations resolve the identifier to an unencoded path, enabling the attacker to overwrite or read arbitrary files inside the data directory, trigger crashes through metadata inconsistencies, or achieve code execution via corrupted on-disk structures.

text
// Patch excerpt from sql/ha_partition.cc (MDEV-40362)
-    tablename_to_filename(part_elem->partition_name, part_name,
-                          FN_REFLEN);
+    if (error_if_mysql50_prefix(part_elem->partition_name, ER_WRONG_PARTITION_NAME))
+      DBUG_RETURN(TRUE);
+    if (!tablename_to_filename(part_elem->partition_name, part_name, FN_REFLEN))
+      DBUG_RETURN(TRUE);
     part_name_len= strlen(part_name);

Source: MariaDB Commit f277eef

The patch introduces an explicit error_if_mysql50_prefix() check that rejects partition names carrying the legacy prefix and validates the return of tablename_to_filename() before further processing.

Stop Remote Code Execution Before It Runs

Singularity™ Endpoint detects and blocks exploit attempts at machine speed, including zero-days and novel attack techniques.

Stop Exploit Attempts

Detection Methods for CVE-2026-92262

Indicators of Compromise

  • DDL or DML statements containing the literal string #mysql50# within table, partition, or database identifiers in MariaDB query logs.
  • Unexpected files in the MariaDB data directory whose names begin with #mysql50# or lack the standard filename encoding.
  • Unexplained crashes, assertion failures, or ER_WRONG_PARTITION_NAME errors in the MariaDB error log following table or partition manipulation.

Detection Strategies

  • Enable the MariaDB general query log and alert on any statement containing the #mysql50# token.
  • Monitor the data directory for file creation events on paths that bypass the standard @ or # filename encoding scheme.
  • Correlate client sessions issuing suspicious DDL with privilege level; low-privilege accounts creating partitioned tables with legacy prefixes warrant investigation.

Monitoring Recommendations

  • Ingest MariaDB audit plugin logs into a centralized SIEM and apply detection rules for the #mysql50# identifier pattern.
  • Baseline normal DDL activity per application account to surface anomalous schema modifications.
  • Track file integrity on the MariaDB data directory to detect unauthorized reads, writes, or deletions outside expected table I/O.

How to Mitigate CVE-2026-92262

Immediate Actions Required

  • Upgrade MariaDB to a fixed release: 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, or 13.0.2.
  • Audit existing databases for table or partition names containing #mysql50# and rename or drop any that are not required for legacy compatibility.
  • Restrict CREATE, ALTER, and partition management privileges to the minimum set of accounts required for operations.

Patch Information

MariaDB released fixes in the upstream commits 574ba66 and f277eef, tracked as MDEV-40362 and documented in advisory GHSA-65jj-h265-3m7h. Fixed binaries are available in the 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2 releases.

Workarounds

  • Revoke CREATE and partition-related privileges from application accounts that do not require schema modification.
  • Block or rewrite inbound SQL containing the #mysql50# token at proxy or firewall layers until patching is complete.
  • Isolate MariaDB instances behind network segmentation so that only trusted application tiers can reach the database port.
bash
# Verify installed MariaDB version and check for vulnerable identifiers
mysql -u root -p -e "SELECT VERSION();"
mysql -u root -p -e "SELECT table_schema, table_name FROM information_schema.tables WHERE table_name LIKE '%#mysql50#%';"

# Debian/Ubuntu upgrade example
sudo apt-get update
sudo apt-get install --only-upgrade mariadb-server
sudo systemctl restart mariadb

Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.

Sources: National Vulnerability Database, CISA KEV, Exploit-DB

Experience the Most Advanced Cybersecurity Platform

See how the world’s most intelligent, autonomous cybersecurity platform can protect your organization today and into the future.