Strix
74.1K

CVE-2026-92262

CRITICALCVSS 9.9/10EPSS 0.68%

Last modified

CVE-2026-92262 is a critical-severity vulnerability rated 9.9/10 on the CVSS scale. 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. EPSS estimates a 0.68% chance of exploitation in the next 30 days.

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.

Metrics

CVSS 3.1
9.9/10

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H

EPSS Probability
0.68%

51.4th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

Affected Software

VendorProductVersions
MariadbMariadb>= 10.6.1, < 10.6.28
MariadbMariadb>= 10.11.1, < 10.11.19
MariadbMariadb>= 11.4.1, < 11.4.13
MariadbMariadb>= 11.8.1, < 11.8.9
MariadbMariadb>= 12.3.1, < 12.3.3
MariadbMariadb13.0.1

References

Timeline

Published
Last Modified
Status
Analyzed

Frequently Asked Questions

What is 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.
How severe is CVE-2026-92262?
CVE-2026-92262 has a CVSS score of 9.9/10 (CRITICAL severity). The EPSS model estimates a 0.68% probability of exploitation in the next 30 days.
How do I fix CVE-2026-92262?
Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

How Strix Helps

Related CVEs from 2026

View all 2026CVEs →

Are you affected by CVE-2026-92262?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST