Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
9.9

CVE-2026-92262: MariaDB server table name trick lets attackers steal data

CVE-2026-92262 · published today
Summary

Certain older versions of MariaDB server let a specially crafted table name bypass normal file protections. An attacker could use this to cause crashes, corrupt or steal data, or even run code on your system. Upgrade to the latest MariaDB releases that fix the issue as soon as possible.

What to do
  • Update bellsoft mariadb to version 10.6.28-r0.
  • Update bellsoft mariadb to version 11.8.9-r0.
Affected software
Ecosystem VendorProductAffected versions
Alpaquita:23 bellsoft mariadb >= 10.6.12-r0, < 10.6.28-r0
Fix: upgrade to 10.6.28-r0
Alpaquita:stream bellsoft mariadb >= 10.11.4-r0, < 11.8.9-r0
Fix: upgrade to 11.8.9-r0
Ubuntu:16.04:LTS canonical mariadb-10.0 All versions
Ubuntu:18.04:LTS canonical mariadb-10.1 All versions
Ubuntu:20.04:LTS canonical mariadb-10.3 All versions
Ubuntu:22.04:LTS canonical mariadb-10.6 All versions
Ubuntu:24.04:LTS canonical mariadb All versions
Original advisory text
UBUNTU-CVE-2026-92262
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.
Severity
9.9 Critical
Type
CWE-706Use of Incorrectly-Resolved Name or Reference
Timeline
Published16 Oct 2026
Updated16 Oct 2026
First seen8 Oct 2026
Track software like this
Free during beta