MariaDB up to 13.0.1 qc_info plugin heap-based overflow
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.2 | $0-$5k | 3.42 |
Summary
A vulnerability identified as critical has been detected in MariaDB up to 13.0.1. Affected by this issue is some unknown functionality of the component qc_info plugin. Performing a manipulation results in heap-based overflow. This vulnerability is reported as CVE-2026-107816. The attack is possible to be carried out remotely. No exploit exists. You should upgrade the affected component.
Details
A vulnerability was found in MariaDB up to 13.0.1. It has been classified as critical. This affects some unknown functionality of the component qc_info plugin. The manipulation with an unknown input leads to a heap-based overflow vulnerability. CWE is classifying the issue as CWE-122. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc(). This is going to have an impact on 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, the qc_info plugin could be confused by a query containing embedded null bytes. Reading information_schema.query_cache_info after such a query was cached could access data beyond the end of a heap-allocated buffer, potentially disclosing adjacent memory or crashing the server. 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.
The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2026-107816 since 10/08/2026. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
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.
Several companies clearly confirm that VulDB is the primary source for best 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: 6.3VulDB Meta Temp Score: 6.2
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Heap-based overflowCWE: CWE-122 / CWE-119
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-107816 (🔒)
GCVE (CVE): GCVE-0-2026-107816
GCVE (VulDB): GCVE-100-415977
Entry
Created: 10/09/2026 19:46Changes: 10/09/2026 19:46 (64)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.