Goal Reached Thanks to every supporter — we hit 100%!

Goal: 1000 CNY · Raised: 1359 CNY

100%

CVE-2026-92262— MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass.

Quick assessment

Affected
MariaDB server
Exploitation
No confirmed in-the-wild exploitation; assess based on exposure
Recommended action
Check the vendor advisory and references for a fixed version. If immediate upgrade is impossible, restrict exposure and increase monitoring.

MariaDB 服务器是 MySQL 服务器的社区分支版本。在 MariaDB 10.6.1 至 10.6.28、10.11.19、11.4.13、11.8.9、12.3.3 以及 13.0.2 等版本中, 前缀存在绕过漏洞,该前缀可绕过正常的表名文件系统编码机制。攻击者可通过创建带有 前缀的表名来触发此漏洞,进而利用该前缀以表名的旧式未编码形式访问文件,导致服务崩溃、数据损坏、数据泄露或远程代码执行。该漏洞已在 10.6.28、10.11.19、11.4.13、11.8.9、12.3.3 和 13.0.2 等版本

CVSS 9.9 · Critical

Affected Version Matrix 6

VendorProduct Version RangeStatus
MariaDB server >= 10.6.1, < 10.6.28 affected
>= 10.11.1, < 10.11.19 affected
>= 11.4.1, < 11.4.13 affected
>= 11.8.1, < 11.8.9 affected
>= 12.3.1, < 12.3.3 affected
>= 13.0.1, < 13.0.2 affected
Get alerts for future matching vulnerabilities Log in to subscribe

I. Basic Information for CVE-2026-92262

Vulnerability Information

Have questions about the vulnerability? See if Shenlong's analysis helps!
View Shenlong Deep Dive ↗

Although we use advanced large model technology, its output may still contain inaccurate or outdated information.Shenlong tries to ensure data accuracy, but please verify and judge based on the actual situation.

Vulnerability Title
MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass.
Source: CVE Program / CVE List V5
Vulnerability 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.
Source: CVE Program / CVE List V5
CVSS Information
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Source: CVE Program / CVE List V5
Vulnerability Type
使用不正确的解析名称或索引
Source: CVE Program / CVE List V5

Affected Products

Vendor Product Affected Versions CPE Subscribe
MariaDB server >= 10.6.1, < 10.6.28 -

II. Public POCs for CVE-2026-92262

# POC Description Source Link Shenlong Link
AI-Generated POC Premium

No public POC found.

Login to generate AI POC

III. Intelligence Information for CVE-2026-92262

请登录查看更多情报信息。

Patches & Fixes for CVE-2026-92262 (2)

Vendor Advisories for CVE-2026-92262 (1)

Vendor Pages for CVE-2026-92262 (4)

Other References for CVE-2026-92262 (1)

Same Patch Batch · MariaDB · 2026-10-16 · 7 CVEs total

CVE-2026-85748 9.9 CRITICAL MariaDB: Use-after-free with a large number of SYS_REFCURSOR's
CVE-2026-85746 9.9 CRITICAL MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections
CVE-2026-97380 8.8 HIGH MariaDB: GRANT PROXY with empty password incorrectly checks grantor's privileges
CVE-2026-86047 7.7 HIGH MariaDB: Insufficient quoting in mariadb-dump and SHOW commands
CVE-2026-85985 5.4 MEDIUM MariaDB: Unauthorized file access via CONNECT engine UDFs
CVE-2026-85745 4.3 MEDIUM MariaDB: Out-of-bound buffer read on in `ST_Area` of a multipolygon.

IV. Related Vulnerabilities

V. Comments for CVE-2026-92262

No comments yet


Leave a comment