CVE-2026-107817
Received Received - Intake

Memory Corruption in MariaDB via Invalid JSON Data

Publication date: 2026-10-09

Last updated on: 2026-10-09

Assigner: GitHub, Inc.

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, 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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-09
Last Modified
2026-10-09
Generated
2026-10-10
AI Q&A
2026-10-09
EPSS Evaluated
N/A
NVD
CVE-2026-107817
EUVD
EUVD-2026-95918

Affected Vendors & Products

Showing 6 associated CPEs
Vendor Product Version / Range
MariaDB server >= 10.6.1, < 10.6.28
MariaDB server >= 10.11.1, < 10.11.19
MariaDB server >= 11.4.1, < 11.4.13
MariaDB server >= 11.8.1, < 11.8.9
MariaDB server >= 12.3.1, < 12.3.3
MariaDB server >= 13.0.1, < 13.0.2

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-125 The product reads data past the end, or before the beginning, of the intended buffer.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

This vulnerability affects MariaDB's mysql_json plugin, which parses MySQL binary JSON data. It fails to validate data properly, allowing specially crafted tables with invalid JSON to cause out-of-bounds memory reads, information disclosure, or server crashes. The issue was fixed in updated versions by adding boundary checks to prevent reading beyond allocated memory.

Detection Guidance

Check MariaDB version with 'mysql --version' or 'mariadb --version'. If running affected versions (10.6.1-10.6.27, 10.11.1-10.11.18, 11.4.1-11.4.12, 11.8.1-11.8.8, 12.3.1-12.3.2, 13.0.1), update immediately. Inspect logs for 'Error parsing MySQL JSON format' messages indicating corrupted JSON data handling.

Impact Analysis

An attacker with local access could exploit this to read sensitive memory, crash the MariaDB server, or potentially access unauthorized data. The impact is limited by requiring local access and user interaction. Confidentiality and availability risks are low, but integrity could be affected if memory corruption occurs.

Compliance Impact

This vulnerability could lead to unauthorized data access or disclosure, violating GDPR's data protection principles or HIPAA's confidentiality requirements. Organizations must patch affected systems to maintain compliance and prevent potential breaches.

Mitigation Strategies

Upgrade MariaDB to patched versions (10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2). Uninstall mysql_json plugin if not required. Restrict FILE privileges and set secure-file-priv. Ensure datadir permissions prevent unauthorized file creation.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-107817. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart