Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
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.
Priority
LOW
Exploitation
NONE
PoC
NONE
Patch
NONE
Momentum
NONE
🚨 CVE-2026-92262 (CVSS 9.9 Critical) Historical table name encoding bypass (mysql50) in MariaDB allows remote attackers to access unencoded filesystem data, cause corruption, or achieve remote code execution. https://www.thehackerwire.com/vulnerability/CVE-2026-92262/ https://t.co/qEEh8Rh2me
🚨Critical - MariaDB #mysql50# Table Name Encoding Bypass (CVE-2026-92262) MariaDB Server mishandles the historical #mysql50# prefix, letting crafted table names bypass filesystem table-name encoding and resolve legacy unencoded paths. An attacker with SQL CREATE/RENAME privileges can target unexpected files, causing crashes, data corruption, data exfiltration, or potential RCE. 👉Affected: MariaDB Server < 10.6.28, < 10.11.19, < 11.4.13, < 11.8.9, < 12.3.3, < 13.0.2 | Upgrade to 10.6.28/10.11.19/11.4.13/11.8.9/12.3.3/13.0.2