# CVE-2026-32710: Heap-based Buffer Overflow in MariaDB > An authenticated user can crash MariaDB via a heap buffer overflow in JSON_SCHEMA_VALID, potentially leading to remote code execution under specific memory conditions. - **Severity:** High 8.6 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** Any signed-in user - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 20 Mar 2026 - **Updated:** 27 Mar 2026 - **Also known as:** BELL-CVE-2026-32710, BIT-mariadb-2026-32710, BIT-mariadb-min-2026-32710, BIT-mysql-client-2026-32710, DEBIAN-CVE-2026-32710, GHSA-4rj5-2227-9wgc, MINI-2cmh-p8vf-rg79, MINI-3875-x9pp-jpcg, MINI-5wg8-vrv5-mf7h, MINI-gvxq-vcqx-7g96, RHSA-2026:19021, RHSA-2026:19182, RLSA-2026:19021, RLSA-2026:19182, SUSE-SU-2026:1367-1, SUSE-SU-2026:21407-1, UBUNTU-CVE-2026-32710, openSUSE-SU-2026:10694-1, openSUSE-SU-2026:20629-1 ## What is CVE-2026-32710? CVE-2026-32710 is a high-severity memory corruption vulnerability in Mariadb Mariadb, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. ### Official description 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. Weakness: CWE-122 (Heap-based Buffer Overflow) ## Which versions are affected by CVE-2026-32710? 3 open source packages ship an affected version, including mariadb, mariadb-min and mysql-client. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mariadb` | Bitnami | From 11.4.1 | 11.4.10, 11.8.6, 12.2.2 | | `mariadb-min` | Bitnami | From 11.4.1 | 11.4.10, 11.8.6, 12.2.2 | | `mysql-client` | Bitnami | From 11.4.1 | 11.4.10, 11.8.6, 12.2.2 | | `galera` | Red Hat:enterprise_linux:10.2 | All versions | 0:26.4.25-1.el10_2 | | `galera-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:26.4.25-1.el10_2 | | `galera-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:26.4.25-1.el10_2 | | `mariadb11.8` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-backup` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-backup-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-client-utils` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-common` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-devel` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-embedded` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-embedded-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-embedded-devel` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-errmsg` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-gssapi-server` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-gssapi-server-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-oqgraph-engine` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-oqgraph-engine-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-pam` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-pam-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-server` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-server-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-server-galera` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-server-galera-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-server-utils` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-test` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `mariadb11.8-test-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 3:11.8.6-2.el10_2 | | `galera` | Red Hat:enterprise_linux:9::appstream | All versions | 0:26.4.25-1.module+el9.8.0+24146+e179c349 | | `galera-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:26.4.25-1.module+el9.8.0+24146+e179c349 | | `galera-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:26.4.25-1.module+el9.8.0+24146+e179c349 | | `mariadb` | Red Hat:enterprise_linux:9::appstream | All versions | 3:11.8.6-2.module+el9.8.0+24146+e179c349 | | `mariadb-backup` | Red Hat:enterprise_linux:9::appstream | All versions | 3:11.8.6-2.module+el9.8.0+24146+e179c349 | | `mariadb-backup-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 3:11.8.6-2.module+el9.8.0+24146+e179c349 | | `mariadb-client-utils` | Red Hat:enterprise_linux:9::appstream | All versions | 3:11.8.6-2.module+el9.8.0+24146+e179c349 | | `mariadb-common` | Red Hat:enterprise_linux:9::appstream | All versions | 3:11.8.6-2.module+el9.8.0+24146+e179c349 | | `mariadb-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 3:11.8.6-2.module+el9.8.0+24146+e179c349 | Products: Mariadb Mariadb. ## How do I fix CVE-2026-32710? Upgrade mariadb to a fixed version for your release line: 11.4.10, 11.8.6 or 12.2.2. ## Is CVE-2026-32710 being exploited? There is no known exploitation of CVE-2026-32710 in the wild and no public exploit code. Public exploit code: - Heap OOB write in MariaDB JSON_SCHEMA_VALID() → persistent privilege escalation (lab-assisted) (github_poc): https://github.com/dinosn/CVE-2026-32710 ## Other vulnerabilities in Mariadb Mariadb - [CVE-2026-49261](https://insights.sbomify.com/CVE-2026-49261/): MariaDB server has unsafe parameter handling in `wsrep_notify_cmd` (critical 10.0) - [CVE-2026-85746](https://insights.sbomify.com/CVE-2026-85746/): MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections (critical 9.9) - [CVE-2026-85748](https://insights.sbomify.com/CVE-2026-85748/): MariaDB: Use-after-free with a large number of SYS_REFCURSOR's (critical 9.9) - [CVE-2026-92262](https://insights.sbomify.com/CVE-2026-92262/): MariaDB: Numerous issues caused by historical #mysql50# tablename encoding bypass. (critical 9.9) - [CVE-2023-26785](https://insights.sbomify.com/CVE-2023-26785/): Code injection in n/a (critical 9.8) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-32710 and fix it if it is affected. What it is: CVE-2026-32710 is a high-severity memory corruption vulnerability in Mariadb Mariadb, published on 20 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-32710 in the wild and no public exploit code. Affected packages and fixed versions: - mariadb (Bitnami): affected from 11.4.1; fixed in 11.4.10, 11.8.6, 12.2.2 - mariadb-min (Bitnami): affected from 11.4.1; fixed in 11.4.10, 11.8.6, 12.2.2 - mysql-client (Bitnami): affected from 11.4.1; fixed in 11.4.10, 11.8.6, 12.2.2 Task: 1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies. 2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it. 3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead. 4. Run the tests and summarise what changed and why. 5. If nothing in the project is affected, say so and change nothing. Reference: https://insights.sbomify.com/CVE-2026-32710/ (Markdown: https://insights.sbomify.com/CVE-2026-32710/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32710 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32710 - OSV: https://osv.dev/vulnerability/CVE-2026-32710 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-32710/ Summaries are generated and may contain mistakes; the official description above is the record.