cve.bz

CVE-2026-92262 mariadb mariadb

9.9 criticalEPSS 1.5%Fix available

Critical (9.9) in mariadb mariadb. EPSS 1.5% estimated probability of exploitation activity in the next 30 days.

On this page
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

CVSS 3.1

9.9 critical
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS
1.5% (unchanged from 1.5% a week ago; 0.7% 30 days ago) estimated probability of exploitation activity in the next 30 days; 74th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: none · Automatable: no · Technical impact: total, assessed 2026-10-21. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-706 Use of Incorrectly-Resolved Name or Reference
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-92262 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-92262?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-92262?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-92262 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the NVD's CPE matches.

ProductAffected
mariadb:mariadbfrom 10.6.1 before 10.6.28
mariadb:mariadbfrom 10.11.1 before 10.11.19
mariadb:mariadbfrom 11.4.1 before 11.4.13
mariadb:mariadbfrom 11.8.1 before 11.8.9
mariadb:mariadbfrom 12.3.1 before 12.3.3
mariadb:mariadb13.0.1

Linux distributions

DistributionReleasePackageFixed inAdvisory
Debian12mariadb10.11.19-0+deb12u1DEBIAN-CVE-2026-92262
Debian13mariadbno fix listedDEBIAN-CVE-2026-92262
Debian14mariadb1:11.8.9+ds-1DEBIAN-CVE-2026-92262
Ubuntu16.04:LTSmariadb-10.0no fix listedUBUNTU-CVE-2026-92262
Ubuntu18.04:LTSmariadb-10.1no fix listedUBUNTU-CVE-2026-92262
Ubuntu20.04:LTSmariadb-10.3no fix listedUBUNTU-CVE-2026-92262
Ubuntu22.04:LTSmariadb-10.6no fix listedUBUNTU-CVE-2026-92262
Ubuntu24.04:LTS, 26.04:LTS, 26.10mariadbno fix listedUBUNTU-CVE-2026-92262
Red Hathummingbird:1mariadb10.11, mariadb10.11-pam, mariadb10.11-test and 17 more3:10.11.18-4.1.10.hum1RHSA-2026:92905
openSUSETumbleweedmariadb12.3.2-3.1openSUSE-SU-2026:12245-1
Alpaquita23mariadb10.6.28-r0BELL-CVE-2026-92262
Alpaquita25mariadb11.4.13-r0BELL-CVE-2026-92262
Alpaquitastreammariadb11.8.9-r0BELL-CVE-2026-92262

From the distributions' data via OSV.dev: the Debian Security Tracker; Ubuntu Security Notices © Canonical Ltd., CC BY-SA 4.0; Red Hat Security Data © Red Hat, Inc., CC BY 4.0; SUSE security data, CC BY 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Debian · Ubuntu · Red Hat · openSUSE · Alpaquita.

Red Hat

Red Hat rates this Important.

Red Hat's statement

Red Hat Product Security rates this vulnerability as having an Important severity because an authenticated database user can achieve arbitrary code execution, exfiltrate data, or crash the database service across a network boundary, resulting in a severe compromise of system confidentiality and availability. While default deployments of MariaDB in Red Hat environments restrict direct network connectivity and require valid authentication credentials to submit queries, any user with table-level interaction capabilities can exploit the flaw without needing administrative privileges. The severity is elevated beyond Moderate because bypassing filesystem name encoding can breach the database sandbox and access underlying host files, though the prerequisite of existing database credentials prevents this from reaching Critical severity.

Red Hat's mitigation

Upgrade to the fixed version of MariaDB Server

ProductPackageStateAdvisory
Red Hat Hardened Imagesmariadb10-11-main-10.11.18-4.1.10.hum1Fixed 2026-10-29RHSA-2026:92905
Red Hat Enterprise Linux 10mariadb10.11Affected
Red Hat Enterprise Linux 10mariadb11.8Affected
Red Hat Enterprise Linux 7mariadbAffected
Red Hat Enterprise Linux 8mariadb:10.11/mariadbAffected
Red Hat Enterprise Linux 8mariadb:10.3/mariadbAffected
Red Hat Enterprise Linux 9mariadbAffected
Red Hat Enterprise Linux 9mariadb:10.11/mariadbAffected
Red Hat Enterprise Linux 9mariadb:11.8/mariadbAffected
Red Hat Hardened Imageshi/mariadbNot affected
Red Hat Hardened Imagesmariadb11.8Not affected
Red Hat OpenStack Platform 13 (Queens)mariadbAffected

Contains Red Hat Security Data © Red Hat, Inc., licensed under CC BY 4.0. Source: https://access.redhat.com/security/data. Modified: reformatted. Red Hat's page for CVE-2026-92262.

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it. How Harbor Check reads them, and what it found.

  • SeanDishman/mariadb-cve-2026-92262 Harbor Check: matches CVE 1 star, Python, created
    PoC for CVE-2026-92262, CVE-2026-85746, CVE-2026-85748 against MariaDB 13.0.1

Attack patterns (CAPEC)

  • CAPEC-48 Passing Local Filenames to Functions That Expect a URL Likelihood: High · Severity: High
  • CAPEC-159 Redirect Access to Libraries Likelihood: High · Severity: Very High
  • CAPEC-177 Create files with the same name as files protected with a higher classification Severity: Very High
  • CAPEC-641 DLL Side-Loading Likelihood: Low · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON