CVE-2026-107817·MariaDB vulnerability
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 mysql_json plugin assumed that imported MySQL tables contained valid MySQL binary JSON data. A specially prepared MySQL table containing invalid JSON data could cause out-of-bounds reads, information disclosure, or a server crash. 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.
- Severity
- medium
- Software
- MariaDB
- Fixed in
- 13.0.2
- Published
How likely is exploitation
FIRST's Exploit Prediction Scoring System puts the probability of this CVE being exploited in the next 30 days at 0.12% — higher than 2% of all published CVEs. EPSS is an independent forecast of exploitation, not a severity rating: it says nothing about how much damage a successful attack does, which is what a CVSS score measures.
Affected versions
From: 13.0.1
Until: 13.0.2
Fixed in: 13.0.2
How to fix this CVE
Update MariaDB to version 11.8.9 or later to resolve a vulnerability in the mysql_json plugin that fails to validate imported JSON data properly. Unpatched servers running versions 10.6.1 through 13.0.1 are at risk of crashes, information leaks, and memory corruption when processing malformed JSON structures from imported MySQL tables. Apply the security patch immediately and test the upgrade in a non-production environment first.
sudo dnf update mariadb-serverDefensia detects this vulnerability
How to check if you are affected
- Check installed MariaDB version: mysql --version or mariadb --version
- Query the server version within MariaDB: SELECT VERSION(); from any MySQL client
- List all installed plugins to confirm mysql_json is active: SELECT PLUGIN_NAME, PLUGIN_STATUS FROM INFORMATION_SCHEMA.PLUGINS WHERE PLUGIN_NAME LIKE '%json%';
- Verify the patch was applied by confirming the version matches or exceeds 11.8.9, 11.4.13, 12.3.3, or 13.0.2 depending on your release series
FAQ
What is CVE-2026-107817?
This vulnerability affects MariaDB's mysql_json plugin, which fails to validate binary JSON data during table imports. Attackers with database access can craft malicious MySQL tables with corrupted JSON to trigger out-of-bounds memory reads, causing server crashes or leaking sensitive information.
Is CVE-2026-107817 being actively exploited?
No, there are currently no public exploits or active exploitation campaigns targeting this vulnerability in the wild.
What versions of MariaDB are affected by CVE-2026-107817?
Affected versions include 10.6.1–10.6.27, 10.11.0–10.11.18, 11.4.0–11.4.12, 11.8.0–11.8.8, 12.3.0–12.3.2, and 13.0.0–13.0.1. Fixed versions are 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2 or later.
How do I check if my server is vulnerable to CVE-2026-107817?
Run SELECT VERSION(); in MariaDB and compare the output to the affected ranges listed above. If your version falls within the vulnerable range, your server needs patching immediately.
Does Defensia detect CVE-2026-107817?
Yes — Defensia's CVE advisory scanner compares installed package versions against the NVD database. If MariaDB is installed on a monitored server, CVE-2026-107817 will appear in your dashboard with remediation steps.
Related MariaDB CVEs
References
- https://github.com/MariaDB/server/commit/851f52470d470a96a66e0b7e5599f3b6c2e45907
- https://github.com/MariaDB/server/releases/tag/mariadb-10.11.19
- https://github.com/MariaDB/server/releases/tag/mariadb-10.6.28
- https://github.com/MariaDB/server/releases/tag/mariadb-11.4.13
- https://github.com/MariaDB/server/releases/tag/mariadb-11.8.9
Track CVEs across your fleet automatically
Defensia scans your Linux servers and tells you exactly which ones are running vulnerable versions — including CVE-2026-107817. Free for 1 server.
Get started free