MariaDB up to 13.0.1 Acl Cache privileges management
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 7.6 | $0-$5k | 0.86 |
Summary
A vulnerability marked as very critical has been reported in MariaDB up to 13.0.1. This vulnerability affects unknown code of the component Acl Cache. The manipulation leads to privileges management. This vulnerability is traded as CVE-2026-107822. It is possible to initiate the attack remotely. There is no exploit available. It is suggested to upgrade the affected component.
Details
A vulnerability was found in MariaDB up to 13.0.1. It has been rated as very critical. This issue affects an unknown code of the component Acl Cache. The manipulation with an unknown input leads to a privileges management vulnerability. Using CWE to declare the problem leads to CWE-269. The product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. Impacted is confidentiality, integrity, and availability. The summary by CVE is:
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.
It is possible to read the advisory at github.com. The identification of this vulnerability is CVE-2026-107822 since 10/08/2026. The exploitation is known to be easy. The attack may be initiated remotely. Additional levels of successful authentication are needed for exploitation. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 10/09/2026). The attack technique deployed by this issue is T1068 according to MITRE ATT&CK.
Upgrading to version 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3 or 13.0.2 eliminates this vulnerability.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Name
Version
- 10.6.0
- 10.6.1
- 10.6.2
- 10.6.3
- 10.6.4
- 10.6.5
- 10.6.6
- 10.6.7
- 10.6.8
- 10.6.9
- 10.6.10
- 10.6.11
- 10.6.12
- 10.6.13
- 10.6.14
- 10.6.15
- 10.6.16
- 10.6.17
- 10.6.18
- 10.6.19
- 10.6.20
- 10.6.21
- 10.6.22
- 10.6.23
- 10.6.24
- 10.6.25
- 10.6.26
- 10.6.27
- 10.11.0
- 10.11.1
- 10.11.2
- 10.11.3
- 10.11.4
- 10.11.5
- 10.11.6
- 10.11.7
- 10.11.8
- 10.11.9
- 10.11.10
- 10.11.11
- 10.11.12
- 10.11.13
- 10.11.14
- 10.11.15
- 10.11.16
- 10.11.17
- 10.11.18
- 11.4.0
- 11.4.1
- 11.4.2
- 11.4.3
- 11.4.4
- 11.4.5
- 11.4.6
- 11.4.7
- 11.4.8
- 11.4.9
- 11.4.10
- 11.4.11
- 11.4.12
- 11.8.0
- 11.8.1
- 11.8.2
- 11.8.3
- 11.8.4
- 11.8.5
- 11.8.6
- 11.8.7
- 11.8.8
- 12.3.0
- 12.3.1
- 12.3.2
- 13.0.0
- 13.0.1
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 7.8VulDB Meta Temp Score: 7.6
VulDB Base Score: 9.1
VulDB Temp Score: 8.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.4
CNA Vector (GitHub_M): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Privileges managementCWE: CWE-269 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: MariaDB 10.6.28/10.11.19/11.4.13/11.8.9/12.3.3/13.0.2
Timeline
10/08/2026 CVE reserved10/09/2026 Advisory disclosed
10/09/2026 VulDB entry created
10/09/2026 VulDB entry last update
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2026-107822 (🔒)
GCVE (CVE): GCVE-0-2026-107822
GCVE (VulDB): GCVE-100-415979
Entry
Created: 10/09/2026 19:47Changes: 10/09/2026 19:47 (64)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.