MariaDB server is a community developed fork of MySQL server. An authenticated user can crash MariaDB versions 11.4 before 11.4.10 and 11.8 before 11.8.6 via a bug in JSON_SCHEMA_VALID() function. Under certain conditions it might be possible to turn the crash into a remote code execution. These conditions require tight control over memory layout which is generally only attainable in a lab environment. This issue is fixed in MariaDB 11.4.10, MariaDB 11.8.6, and MariaDB 12.2.2.
CVE-2026-32710
HIGHNVD 9.98.6Trending — 4 sources updated this weekElevated
EchelonGraph scoreLOW confidence
This high-severity CVE scores 8.6 under the CNA's CVSS (NVD's own analysis pending). EPSS exploit-prediction score not yet available (the EPSS model rescores nightly; freshly-published CVEs typically appear within 48 hours). GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: cna:github_m
8.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
- High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.9Exploit: Elevated riskExposed: 0
A fix is available — apply it.
- CVSS v3
- 9.9
- EG Score
- 8.6(low)
- EG Risk
- 55(Track)EG Risk 55/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity86% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 1%
- EPSS %ILE
- 55%
- KEV
- Not listed
Published
March 20, 2026
Last Modified
June 17, 2026
Advisory Details (2)
Auto-updated Jul 27, 2026Patch available. Sources: github.
generic
[MDEV-38356] JSON_SCHEMA_VALID() crashes with a long enum - Jira
https://jira.mariadb.org/browse/MDEV-38356github Patch Available
Heap-based Buffer Overflow in JSON_SCHEMA_VALID() · Advisory · MariaDB/server · GitHub
https://github.com/MariaDB/server/security/advisories/GHSA-4rj5-2227-9wgcVendor Advisories for CVE-2026-32710(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Patch Availability(2)
| Vendor / Ecosystem | Fixed in / Patch | Released | Source |
|---|---|---|---|
| redhat | mariadb11.8-3:11.8.6-2.el10_2 | 2026-05-19 | redhat |
| redhat | mariadb:11.8-9080020260330112902.rhel9 | 2026-05-19 | redhat |
Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 4× in last 7d / 4× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-27 14:13 UTCEPSS rescore
- 2026-07-27 12:51 UTCEG score recompute
- 2026-07-27 12:51 UTCVendor advisory
- 2026-07-27 12:50 UTCOSV refresh
Publicly available exploits
(1 reference)Working exploit code is in the public domain (1 GitHub PoC). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.
- GitHub PoCdinosn/CVE-2026-32710First seen May 6, 2026
Heap OOB write in MariaDB JSON_SCHEMA_VALID() → persistent privilege escalation (lab-assisted)
Open source ↗
Frequently asked(5)
What is CVE-2026-32710?
CVE-2026-32710 is a high vulnerability published on March 20, 2026. MariaDB server is a community developed fork of MySQL server. An authenticated user can crash MariaDB versions 11.4 before 11.4.10 and 11.8 before 11.8.6 via a bug in JSONSCHEMAVALID() function. Under certain conditions it might be possible to turn the crash into a remote code execution. These…
When was CVE-2026-32710 disclosed?
CVE-2026-32710 was first published in the National Vulnerability Database on March 20, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-32710 actively exploited?
CVE-2026-32710 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 45.3% of all scored CVEs.
What is the CVSS score of CVE-2026-32710?
CVE-2026-32710 has a CVSS v3 base score of 9.9 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 8.6. The EG score is currently aggregating — additional source signals are being incorporated as they become available..
How do I remediate CVE-2026-32710?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-32710, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-32710
Is Your Infrastructure Affected by CVE-2026-32710?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.