CVE-2026-102523: MariaDB server: Authorization bypass via ALTER TABLE ... CONVERT ... PARTITION

Published Nov 5, 2026
·
Updated

MariaDB server is a community developed fork of MySQL server. From 10.11.1 until 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, ALTER TABLE ... CONVERT ... PARTITION does not apply filename encoding to user-specified partition names before using them in filesystem path construction. An authenticated database user can use a partition name requiring filename escaping to make the conversion operate on table files the user is not authorized to access, allowing unauthorized table reads or modifications. This issue is fixed in versions 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade MariaDB server to a version that resolves this vulnerability.

    Fixed in 10.11.19
  2. Upgrade

    Upgrade MariaDB server to a version that resolves this vulnerability.

    Fixed in 11.4.13
  3. Upgrade

    Upgrade MariaDB server to a version that resolves this vulnerability.

    Fixed in 11.8.9
  4. Upgrade

    Upgrade MariaDB server to a version that resolves this vulnerability.

    Fixed in 12.3.3
  5. Upgrade

    Upgrade MariaDB server to a version that resolves this vulnerability.

    Fixed in 13.0.2

Event History

Nov 5, 2026
CVE Published
via MITRE·03:31 PM
Data Sourced
via MITRE·03:31 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are affected?

MariaDB Server deployments running versions from 10.11.1 through versions before the listed fixes are affected. The issue is fixed in 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.

2

What access does an attacker need?

An attacker needs an authenticated MariaDB database account and must be able to issue an ALTER TABLE ... CONVERT ... PARTITION operation with a user-specified partition name requiring filename escaping. No unauthenticated attack path is described.

3

What is the potential impact?

A successful exploit can cause the conversion operation to act on table files that the database user is not authorized to access. This can allow unauthorized reads or modifications of tables.

4

What should be done to remediate the issue?

Upgrade to MariaDB Server 10.11.19, 11.4.13, 11.8.9, 12.3.3, or 13.0.2, as appropriate for the deployed release branch.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203