CVE-2026-92262

9.9Critical

Published 16 Oct 2026 · NVD status: Awaiting Analysis · AI triage by gemini-3.8-flash

9.9Critical

Attack vector: Network
Complexity: Low
Privileges needed: Low
User interaction: None
Impact: Full C/I/A compromise
Weakness: CWE-706

Impact

Authenticated attackers with network access can cause crashes, data corruption, exfiltrate data, or execute arbitrary code. They need low-privileged database access to create or query crafted table names.

Root cause

The #mysql50# prefix bypasses table-name filesystem encoding, allowing access to underlying files via legacy unencoded names.

Affected systems

MariaDB server versions 10.6.1 through 10.6.27, and versions prior to 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2

CVSS v3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

Fix & remediation

Upgrade MariaDB server to version 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2, or higher. No interim configuration mitigation is provided, so restrict untrusted database account access until patched.

shell

$ mariadb --version

AI-suggested. Run it in staging first and check it against the vendor advisory. Why?

Ad · In-content banner

NVD 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.

References

Source: nvd.nist.gov/vuln/detail/CVE-2026-92262