CVE-2026-107822

MariaDB: database privilege escalation via user / role name collision in the acl cache

Published Oct 9, 2026 CVSS 3.1 · 6.4 Medium EPSS < 1% KEV · Not listed
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, MariaDB's ACL cache could generate the same database-privilege cache key for role and localhost user names that matched because both used an empty IP component. An attacker with CREATE USER could create the colliding principal and, when the original principal's database privileges were cached, exercise privileges assigned to the other account. 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.

Analysis

AI-generated

Technical impact

MariaDB Server's ACL cache can generate identical keys for a role and a localhost user when both use an empty IP component. An attacker who can issue CREATE USER statements can create a principal that collides with an existing one, causing the cache to hold privileges for the wrong account. The attacker then gains the privileges assigned to the original account, effectively escalating their own access. The flaw is a collision in cache key handling and performs an unintended privilege escalation, represented by the CWE identifiers in the advisory.

Affected Systems

Affected are MariaDB Server installations in the following releases: 10.6.1‑10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2. All community‑derived MariaDB Server products in these versions are vulnerable until patched.

Risk and Exploitability

The CVSS base score is 6.4, indicating medium severity. The EPSS score is not available and the vulnerability is not listed in the CISA KEV catalog, so the public exploitation probability cannot be determined from available data. The likely attack vector is a local attacker with CREATE USER privileges; thus the risk is highest in environments where user creation is broadly granted. No public exploits have been reported, but the potential to acquire any database privileges makes this a significant concern for administrators who do not tightly control user creation.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade MariaDB Server to version 10.6.28 or newer (e.g., 10.11.19, 11.4.13, 11.8.9, 12.3.3, or 13.0.2) to apply the official fix.
  • Limit the granting of CREATE USER privileges to trusted administrators only.
  • Review the database for users or roles named "localhost" that could collide with other accounts, and rename or drop them as appropriate, ensuring unique ACL cache keys.

Generated by OpenCVE AI on October 10, 2026 at 01:21 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Mariadb mariadb
CPEs cpe:2.3:a:mariadb:mariadb:*:*:*:*:*:*:*:*
Vendors & Products Mariadb mariadb
Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}

Type Values Removed Values Added
First Time appeared Mariadb
Mariadb server
Vendors & Products Mariadb
Mariadb server
Type Values Removed Values Added
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, MariaDB's ACL cache could generate the same database-privilege cache key for role and localhost user names that matched because both used an empty IP component. An attacker with CREATE USER could create the colliding principal and, when the original principal's database privileges were cached, exercise privileges assigned to the other account. 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.
Title MariaDB: database privilege escalation via user / role name collision in the acl cache
Weaknesses CWE-706
CWE-863
References
Metrics cvssV3_1

{'score': 6.4, 'vector': 'CVSS:3.1/AV:N/AC:H/PR:H/UI:R/S:U/C:H/I:H/A:H'}

Weaknesses
  • CWE-694

    Use of Multiple Resources with Duplicate Identifier

  • CWE-706

    Use of Incorrectly-Resolved Name or Reference

  • CWE-863

    Incorrect Authorization

Sources

Status
PUBLISHED
Assigner
GitHub_M
Published
Updated
Oct 13, 2026, 8:27 PM
Reserved
Oct 8, 2026, 9:23 PM
Status
Analyzed
Published
Oct 9, 2026, 6:17 PM
Modified
Oct 14, 2026, 2:13 PM
Severity
Moderate
Public date
Oct 9, 2026, 5:28 PM