CVE-2026-32710

CRITICALNVD 9.99.9—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.9 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 45% of all CVEs by exploit prediction. 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: epss, nvd
Elevated
9.9EG
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.

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.

CVSS v3
9.9
EG Score
9.9(medium)
EG Risk
61(Track)
EG Risk 61/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 computed
Severity99% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
57%
KEV
Not listed

Published

March 20, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Sep 14, 2026
Patch available. Sources: github.
generic

[MDEV-38356] JSON_SCHEMA_VALID() crashes with a long enum - Jira

https://jira.mariadb.org/browse/MDEV-38356
github Patch Available

Heap-based Buffer Overflow in JSON_SCHEMA_VALID() · Advisory · MariaDB/server · GitHub

https://github.com/MariaDB/server/security/advisories/GHSA-4rj5-2227-9wgc

Vendor 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 / EcosystemFixed in / PatchReleasedSource
redhatmariadb11.8-3:11.8.6-2.el10_22026-05-19redhat
redhatmariadb:11.8-9080020260330112902.rhel92026-05-19redhat

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.

Affected Packages

(2 across 2 ecosystems)
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mariadb1:11.8.2-1 ... 1:11.8.5-4 (10 versions)1:11.8.6-0+deb13u1—
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mariadb1:11.8.2-1 ... 1:11.8.5-4 (9 versions)1:11.8.6-1—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 6× in last 7d / 28× 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.

  1. 2026-09-18 19:28 UTCEPSS rescore
  2. 2026-09-18 19:27 UTCEPSS rescore
  3. 2026-09-17 19:30 UTCEPSS rescore
  4. 2026-09-16 14:08 UTCEPSS rescore
  5. 2026-09-16 05:15 UTCEPSS rescore
  6. 2026-09-13 16:47 UTCEPSS rescore
  7. 2026-09-12 15:01 UTCEPSS rescore
  8. 2026-09-11 14:52 UTCEPSS rescore
  9. 2026-09-10 09:34 UTCEPSS rescore
  10. 2026-09-08 22:00 UTCEPSS rescore
  11. 2026-09-07 16:01 UTCEPSS rescore
  12. 2026-09-06 13:47 UTCEPSS rescore
  13. 2026-09-06 13:47 UTCEPSS rescore
  14. 2026-09-04 05:06 UTCEPSS rescore
  15. 2026-09-02 16:38 UTCOSV refresh
  16. 2026-09-02 14:11 UTCEPSS rescore
  17. 2026-09-01 13:53 UTCEPSS rescore
  18. 2026-09-01 04:39 UTCEPSS rescore
  19. 2026-09-01 04:39 UTCEPSS rescore
  20. 2026-08-30 19:17 UTCEPSS rescore
  21. 2026-08-30 01:22 UTCEPSS rescore
  22. 2026-08-28 21:41 UTCEPSS rescore
  23. 2026-08-27 14:25 UTCEPSS rescore
  24. 2026-08-26 14:46 UTCEPSS rescore
  25. 2026-08-25 13:49 UTCEPSS rescore
Show 75 more
  1. 2026-08-24 14:17 UTCEPSS rescore
  2. 2026-08-23 00:19 UTCEPSS rescore
  3. 2026-08-21 23:49 UTCEPSS rescore
  4. 2026-08-20 22:55 UTCEPSS rescore
  5. 2026-08-20 22:55 UTCEPSS rescore
  6. 2026-08-19 17:03 UTCEPSS rescore
  7. 2026-08-18 13:48 UTCEPSS rescore
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 14:56 UTCEPSS rescore
  10. 2026-08-16 11:00 UTCEG score recompute
  11. 2026-08-16 11:00 UTCVendor advisory
  12. 2026-08-16 02:14 UTCEPSS rescore
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 23:45 UTCVendor advisory
  15. 2026-08-14 19:49 UTCVendor advisory
  16. 2026-08-14 15:02 UTCVendor advisory
  17. 2026-08-14 11:06 UTCVendor advisory
  18. 2026-08-14 07:10 UTCEG score recompute
  19. 2026-08-14 07:10 UTCVendor advisory
  20. 2026-08-13 22:00 UTCEPSS rescore
  21. 2026-08-13 01:46 UTCVendor advisory
  22. 2026-08-12 21:51 UTCEG score recompute
  23. 2026-08-12 21:51 UTCVendor advisory
  24. 2026-08-12 13:50 UTCEPSS rescore
  25. 2026-08-12 01:19 UTCVendor advisory
  26. 2026-08-11 21:23 UTCEG score recompute
  27. 2026-08-11 21:23 UTCVendor advisory
  28. 2026-08-11 08:31 UTCVendor advisory
  29. 2026-08-11 04:24 UTCEG score recompute
  30. 2026-08-11 04:24 UTCVendor advisory
  31. 2026-08-11 00:00 UTCEPSS rescore
  32. 2026-08-10 13:00 UTCVendor advisory
  33. 2026-08-10 09:03 UTCVendor advisory
  34. 2026-08-10 05:08 UTCVendor advisory
  35. 2026-08-10 01:09 UTCVendor advisory
  36. 2026-08-09 21:12 UTCVendor advisory
  37. 2026-08-09 17:16 UTCEG score recompute
  38. 2026-08-09 17:16 UTCVendor advisory
  39. 2026-08-09 13:46 UTCEPSS rescore
  40. 2026-08-09 13:20 UTCVendor advisory
  41. 2026-08-09 06:44 UTCEG score recompute
  42. 2026-08-09 06:44 UTCVendor advisory
  43. 2026-08-08 16:37 UTCEPSS rescore
  44. 2026-08-08 08:58 UTCVendor advisory
  45. 2026-08-08 05:02 UTCVendor advisory
  46. 2026-08-08 01:06 UTCVendor advisory
  47. 2026-08-07 21:10 UTCVendor advisory
  48. 2026-08-07 17:14 UTCEG score recompute
  49. 2026-08-07 17:14 UTCVendor advisory
  50. 2026-08-06 19:18 UTCEG score recompute
  51. 2026-08-06 19:18 UTCVendor advisory
  52. 2026-08-06 13:46 UTCEPSS rescore
  53. 2026-08-06 09:21 UTCVendor advisory
  54. 2026-08-06 05:23 UTCVendor advisory
  55. 2026-08-06 01:27 UTCEG score recompute
  56. 2026-08-06 01:27 UTCVendor advisory
  57. 2026-08-05 19:17 UTCEPSS rescore
  58. 2026-08-04 15:10 UTCEPSS rescore
  59. 2026-08-04 10:38 UTCEPSS rescore
  60. 2026-08-04 04:31 UTCVendor advisory
  61. 2026-08-04 00:35 UTCEG score recompute
  62. 2026-08-04 00:35 UTCVendor advisory
  63. 2026-08-03 10:36 UTCEPSS rescore
  64. 2026-08-03 00:58 UTCVendor advisory
  65. 2026-08-02 20:06 UTCVendor advisory
  66. 2026-08-02 16:10 UTCEG score recompute▲ 1.30
  67. 2026-08-02 16:10 UTCVendor advisory
  68. 2026-08-02 02:27 UTCEPSS rescore
  69. 2026-08-01 04:16 UTCEPSS rescore
  70. 2026-07-30 16:28 UTCEPSS rescore
  71. 2026-07-30 01:30 UTCEPSS rescore
  72. 2026-07-27 14:13 UTCEPSS rescore
  73. 2026-07-27 12:51 UTCEG score recompute
  74. 2026-07-27 12:51 UTCVendor advisory
  75. 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-32710
    First 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 critical 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 43.2% 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).
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

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-32710

Explore →

Is Your Infrastructure Affected by CVE-2026-32710?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs