Cyber Resilience

CVE-2026-32710

Memory Safety in Mariadb 11.4.1 – 11.4.10

Memory Safety
Published
20 March 2026
Modified
31 March 2026
Patch / advisory
View advisory
CVSS Score v3.1 8.5
Click a component to see what it means
Raw vectorCVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H
EPSS Score 0.0086 55th percentile
Risk Priority 61 floored blend · peak EPSS

Summary

CVE-2026-32710 is a high-severity Heap-based Buffer Overflow (CWE-122) vulnerability in Mariadb Mariadb. Its CVSS base score is 8.5 (High).

Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 45% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SI-10 (Information Input Validation) — see the control section below for these in your framework.

Deeper analysis AI-assisted summary

Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.

CVE-2026-32710 is a heap-based buffer overflow vulnerability (CWE-122) in the JSON_SCHEMA_VALID() function of MariaDB server, a community-developed fork of MySQL server. It affects MariaDB versions 11.4 prior to 11.4.10 and 11.8 prior to 11.8.6. An authenticated user can trigger the issue, leading to a server crash. The vulnerability carries a CVSS v3.1 base score of 8.5 (AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H), reflecting high impact potential despite elevated attack complexity.

An attacker with low-privilege authenticated access over the network can exploit this vulnerability by invoking the flawed JSON_SCHEMA_VALID() function, causing a denial-of-service via server crash. Under specific conditions requiring precise control over memory layout—typically feasible only in controlled lab environments—the crash could potentially escalate to remote code execution, granting high confidentiality, integrity, and availability impacts with a scope change.

MariaDB has addressed the issue in versions 11.4.10, 11.8.6, and 12.2.2. Official advisories, including the GitHub Security Advisory at https://github.com/MariaDB/server/security/advisories/GHSA-4rj5-2227-9wgc and the Jira ticket at https://jira.mariadb.org/browse/MDEV-38356, recommend upgrading to these patched releases as the primary mitigation.

EU & UK References

Vulnerability Data

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…

more

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.

CWE(s)
CWE-122

Related Threats

MITRE ATT&CK Enterprise Techniques

T1068 Exploitation for Privilege Escalation Privilege Escalation
Adversaries may exploit software vulnerabilities in an attempt to elevate privileges.
attack.mitre.org →
T1190 Exploit Public-Facing Application Initial Access
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network.
attack.mitre.org →
T1203 Exploitation for Client Execution Execution
Adversaries may exploit software vulnerabilities in client applications to execute code.
attack.mitre.org →
T1210 Exploitation of Remote Services Lateral Movement
Adversaries may exploit remote services to gain unauthorized access to internal systems once inside of a network.
attack.mitre.org →
T1212 Exploitation for Credential Access Credential Access
Adversaries may exploit software vulnerabilities in an attempt to collect credentials.
attack.mitre.org →
Derived from this CVE’s CWE(s) via the direct CWE→ATT&CK cross-walk.

CVEs Like This One

CVE-2026-44169Same product: Mariadb Mariadb
CVE-2026-44173Same product: Mariadb Mariadb
CVE-2026-44171Same product: Mariadb Mariadb
CVE-2023-26785Same product: Mariadb Mariadb
CVE-2024-27766Same product: Mariadb Mariadb
CVE-2023-39593Same product: Mariadb Mariadb
CVE-2026-44168Same product: Mariadb Mariadb
CVE-2026-49261Same product: Mariadb Mariadb
CVE-2026-48165Same product: Mariadb Mariadb
CVE-2026-44170Same product: Mariadb Mariadb

Affected Assets

mariadb
mariadb
12.1.2 · 11.4.1 — 11.4.10 · 11.8.1 — 11.8.6

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)

—

Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V1.4.1

Mitigating Controls (NIST 800-53 r5) AI

SA-11 Developer Testing and Evaluation good match

Developer testing and evaluation (including fuzzing and memory-error detectors) can discover heap overflows after they have been coded.

SI-10 Information Input Validation good match

Input validation enforces bounds checking on data written to heap buffers, directly stopping the overflow condition from being introduced.

SA-8 Security and Privacy Engineering Principles partial match

Security engineering principles require use of memory-safe constructs and bounds-checked allocation routines that avoid introducing heap overflows.

SI-16 Memory Protection partial match

Memory-protection mechanisms limit the ability of a heap overflow to execute attacker-controlled code or corrupt adjacent structures.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 full match
prevents

Secure-development practices directly require bounds checking and safe memory handling that prevent heap overflows.

ID.RA-01 partial match
prevents

Vulnerability scanning and recording can discover heap-overflow flaws but does not prevent their introduction in code.

PR.PS-02 partial match
prevents

Timely patching removes known heap-overflow instances after they exist.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
finds

Security testing in development and acceptance can detect heap overflows before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates practices that reduce the likelihood of introducing heap overflows.

A.8.26 Application security requirements partial match
prevents

Application security requirements can specify bounds-checking and safe memory APIs that mitigate heap overflows.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture and engineering principles include memory-safety and input-validation controls that address heap overflows.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prescribe techniques (safe functions, bounds checks) that prevent heap-based buffer overflows.

A.8.32 Change management none match
none

Change management ensures controlled deployment of fixes for discovered heap-overflow vulnerabilities.

References