Vulnerability DatabaseCVE-2026-102523

CVE-2026-102523: 
MariaDB Server vulnerability analysis and mitigation

Overview

CVE-2026-102523 is an authorization bypass vulnerability in MariaDB Server affecting the ALTER TABLE ... CONVERT ... PARTITION statement. The flaw allows an authenticated database user to read or modify table files they are not authorized to access by crafting a partition name that requires filesystem filename escaping. Affected versions span multiple branches: 10.11.1–10.11.18, 11.4.1–11.4.12, 11.8.1–11.8.8, 12.3.1–12.3.2, and 13.0.1. The vulnerability was published on November 5, 2026, and carries a CVSS v3.1 base score of 8.0 (High) (GitHub Advisory, Red Hat CVE).

Technical details

The root cause is classified as CWE-73 (External Control of File Name or Path): the CONVERT ... PARTITION code path passed user-supplied partition names to create_partition_name() with the translate flag set to FALSE, meaning names containing characters that require filesystem escaping (e.g., hyphens like foo-bar) were used verbatim in filesystem path construction without being encoded via tablename_to_filename() (GitHub Commit). This mismatch between the user-specified name and the on-disk filename allowed the operation to resolve to a different table's files than intended, bypassing authorization controls. Exploitation requires the attacker to be an authenticated database user with ALTER TABLE privileges, and some user interaction is required per the CVSS scoring (GitHub Advisory). The fix changes the translate parameter to TRUE in both alter_partition_convert_out() and alter_partition_convert_in() functions so partition names are properly encoded before filesystem use (GitHub Commit).

Impact

A successful exploit allows an authenticated database user to read or modify table data in tables they are not authorized to access, resulting in high confidentiality, integrity, and availability impact. The attacker can leverage specially crafted partition names to redirect filesystem operations to arbitrary table files, potentially exposing sensitive data from other database users or corrupting tables. While the attack is network-accessible and low complexity, it is limited in scope to the database server's filesystem and does not directly enable OS-level code execution (GitHub Advisory, Red Hat CVE).

Exploitability

As of the time of publication, there is no public proof-of-concept exploit and no evidence of in-the-wild exploitation (Feedly). The vulnerability is not listed in the CISA Known Exploited Vulnerabilities catalog. The EPSS score is approximately 0.0056 (0.56%), indicating a low probability of exploitation in the near term. The NVD SSVC assessment classifies exploitation as "none" and the attack as non-automatable, reflecting the requirement for authenticated access and user interaction (Feedly).

Exploitation steps

  1. Gain authenticated access: Obtain credentials for a low-privileged MariaDB database account with ALTER TABLE privileges on at least one partitioned table.
  2. Identify target table: Determine the on-disk filename of a restricted table the attacker wishes to access (e.g., sensitive_data). MariaDB encodes certain characters in table filenames using tablename_to_filename() — for example, a partition named foo-bar is stored on disk as foo@002dbar.
  3. Craft malicious partition name: Create or identify a partition whose name, when used without encoding, resolves to the on-disk path of the target table's partition file. For example, a partition named #mysql50#p-2 or a name with special characters that maps to the target file.
  4. Execute ALTER TABLE: Issue ALTER TABLE owned_table CONVERT PARTITION 'crafted_name' TO TABLE target_alias; — because the partition name is not encoded before filesystem path construction, the server operates on the unintended table file.
  5. Read or modify data: Access the converted table alias to read or manipulate data from the unauthorized table, or use CONVERT TABLE ... TO PARTITION to write data back, completing the unauthorized modification (GitHub Advisory, GitHub Commit).

Indicators of compromise

  • Logs: MariaDB general query log entries showing ALTER TABLE ... CONVERT PARTITION statements with partition names containing special characters (e.g., hyphens, #mysql50# prefixes, or URL-encoded sequences) issued by low-privileged users.
  • Logs: Audit log entries showing a user accessing or modifying tables they do not own or have explicit grants on, immediately following an ALTER TABLE CONVERT PARTITION operation.
  • File System: Unexpected renaming or movement of .ibd, .MYD, .MYI, or .par partition files in the MariaDB data directory, particularly files belonging to tables not owned by the executing user.
  • Database: Presence of newly created tables (via CONVERT PARTITION TO TABLE) in schemas owned by a user who should not have access to the source partition data.

Mitigation and workarounds

Upgrade MariaDB Server to one of the patched versions: 10.11.19, 11.4.13, 11.8.9, 12.3.3, or 13.0.2, depending on the active version branch (GitHub Advisory, MariaDB 10.11.19 Release). As a workaround for environments that cannot immediately upgrade, partition support can be disabled by starting MariaDB with the --skip-plugin-partition option, which prevents the vulnerable code path from being reachable (GitHub Advisory). Additionally, restrict ALTER TABLE privileges to only trusted database users as a defense-in-depth measure (Red Hat CVE).

Community reactions

The vulnerability was discovered and reported by Ben Bidner of the Automattic.com Security Team (GitHub Advisory). Security news outlets including CyberSecurityNews, GBHackers, and The Daily Tech Feed covered the broader set of MariaDB security fixes released alongside this CVE, with headlines referencing RCE and data theft risks across the patch batch. The Hacker News included the vulnerability in a weekly recap. OpenSUSE's monthly Tumbleweed update for October 2026 also referenced the fix, indicating broad downstream distribution uptake.

Additional resources

Linux Distribution fix status

Fix availability across major Linux distributions and their releases.

Debian

Fixed

bookworm

mariadb: 10.11.19-0+deb12u1

Fixed

sid

mariadb: 1:11.8.9+ds-1

Fixed

trixie

mariadb: 1:11.8.9+ds-0+deb13u1

Fixed

Ubuntu

Unknown

bionic (esm-apps)

mariadb-10.1

Unknown

devel

mariadb

Unknown

focal (esm-apps)

mariadb-10.3

Unknown

jammy

mariadb-10.6

Unknown

jammy (esm-apps)

mariadb-10.6

Unknown

noble

mariadb

Unknown

noble (esm-apps)

mariadb

Unknown

resolute

mariadb

Unknown

RHEL / CentOS

Affected

RHEL 9

mariadb.src

Affected

RHEL 10

mariadb10.11.src

Affected

Source: This report was generated using AI

Related MariaDB Server vulnerabilities:

CVE ID

Severity

Score

Technologies

Component name

CISA KEV exploit

Has fix

Published date

CVE-2026-92262CRITICAL9.9
  • MariaDB Server logoMariaDB Server
  • mariadb1011-sphinx-engine-debuginfo
NoYesOct 16, 2026
CVE-2026-97380HIGH8.8
  • MariaDB Server logoMariaDB Server
  • mariadb:10.11::mariadb-oqgraph-engine
NoYesOct 16, 2026
CVE-2026-102523HIGH8
  • MariaDB Server logoMariaDB Server
  • mariadb123-rocksdb-engine
NoYesNov 05, 2026
CVE-2026-86047HIGH7.7
  • MariaDB Server logoMariaDB Server
  • mariadb-test
NoYesOct 16, 2026
CVE-2026-85985MEDIUM5.4
  • MariaDB Server logoMariaDB Server
  • mariadb:10.3::Judy
NoYesOct 16, 2026

Free Vulnerability Assessment

Benchmark your Cloud Security Posture

Evaluate your cloud security practices across 9 security domains to benchmark your risk level and identify gaps in your defenses.

Request assessment

Additional Wiz resources

Get a personalized demo

Ready to see Wiz in action?

"Best User Experience I have ever seen, provides full visibility to cloud workloads."
David EstlickCISO
"Wiz provides a single pane of glass to see what is going on in our cloud environments."
Adam FletcherChief Security Officer
"We know that if Wiz identifies something as critical, it actually is."
Greg PoniatowskiHead of Threat and Vulnerability Management