CVE-2026-92262
Received Received - Intake

Path Traversal in MariaDB Server via mysql50# Bypass

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
CVE-2026-92262
EUVD
EUVD-2026-102939

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
MariaDB server >= 10.6.1, < 10.6.28
MariaDB server >= 10.11.1, < 10.11.19
MariaDB server >= 11.4.1, < 11.4.13
MariaDB server >= 11.8.1, < 11.8.9
MariaDB server >= 12.3.1, < 12.3.3
MariaDB server >= 13.0.1, < 13.0.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-706 The product uses a name or reference to access a resource, but the name/reference resolves to a resource that is outside of the intended control sphere.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects MariaDB servers between versions 10.6.1 and 10.6.27, 10.11.1 and 10.11.18, 11.4.1 and 11.4.12, 11.8.1 and 11.8.8, 12.3.1 and 12.3.2, and 13.0.1. It involves the #mysql50# prefix which bypasses normal table-name filesystem encoding. Attackers can use this prefix to access files under their legacy unencoded names, causing crashes, data corruption, data exfiltration, or remote code execution.

Detection Guidance

Check MariaDB server version with: mysql --version. If running versions 10.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, or 13.0.1, the system is vulnerable. Test for the #mysql50# prefix issue by attempting to create tables with that prefix and observing crashes or data corruption.

Impact Analysis

An attacker could exploit this to crash the MariaDB server, corrupt or delete data, steal sensitive information, or execute arbitrary code on the affected system. This could lead to complete compromise of the database server, loss of data integrity, and potential unauthorized access to other systems if the database is connected to a network.

Compliance Impact

This vulnerability could lead to unauthorized data access or exfiltration, violating GDPR's data protection requirements and HIPAA's safeguards for protected health information. Organizations may face regulatory penalties, loss of compliance certifications, and reputational damage if exploited.

Mitigation Strategies

Upgrade MariaDB to patched versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, or 13.0.2 immediately. No workarounds exist, so upgrading is the only mitigation. Avoid creating new tables or databases with the #mysql50# prefix.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-92262. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart