CVE-2026-107817 MariaDB CVE debrief

Who should care

Defenders responsible for MariaDB server instances, particularly those using the mysql_json plugin, should assess exposure and apply patches. This includes operators, platform administrators, vulnerability management teams, and security teams. They should review the official advisory and CVE record to validate affected scope, severity, and vendor guidance. Defenders should also monitor for potential information disclosure or server crashes and review

Why it matters

Defenders should prioritize verifying exposure and applying patches for MariaDB server instances using the mysql_json plugin due to potential information disclosure and server crashes.

• Potential information disclosure due to out-of-bounds reads
• Possible server crashes due to invalid JSON data
• Verification of exposure and patch application required for affected versions

Technical summary

The mysql_json plugin in MariaDB server assumes that imported MySQL tables contain 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. The vulnerability affects MariaDB server versions 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2. Defenders should prioritize verifying exposure and applying patches for MariaDB server instances, particularly those using the mysql_json plugin. The official advisory and CVE record provide additional information on the vulnerability.

Defensive priority

Defenders should prioritize verifying exposure and applying patches for MariaDB server instances, particularly those using the mysql_json plugin.

Recommended defensive actions

• Verify MariaDB server instances for exposure, particularly those using the mysql_json plugin
• Apply patches to affected versions (10.6.1-10.6.28, 10.11.1-10.11.19, 11.4.1-11.4.13, 11.8.1-11.8.9, 12.3.1-12.3.3, 13.0.1-13.0.2)
• Monitor for potential information disclosure or server crashes
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up

Evidence notes

The CVE record and source item provide details on the vulnerability, affected versions, and fixed versions. However, there is limited information on potential exploitation or victim impact. Defenders should verify exposure and apply patches for MariaDB server instances using the mysql_json plugin. The official CVE Program record and NIST NVD detail page provide additional information on the vulnerability. There are no known reports of exploitation in the wild, but defenders should monitor for potential information disclosure or server

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.