MariaDBDatabase / datastore
CVE-2026-32710
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMariaDB 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA use-after-free or similar memory corruption bug in MariaDB's JSON_SCHEMA_VALID() function allows any authenticated user to crash the server. Under lab conditions with tight control over memory layout, this memory corruption could potentially be leveraged for remote code execution.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
MariaDBDatabase / datastore
>= 11.4.1, < 11.4.10>= 11.8.1, < 11.8.6= 12.1.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check MariaDB server versionRun 'SELECT VERSION();' or check the installed package version using 'mysql --version' or your system's package manager (e.g., 'dpkg -l | grep mariadb' or 'rpm -qa | grep mariadb')Affected if The version is 11.4.1 through 11.4.9, 11.8.1 through 11.8.5, or exactly 12.1.2
-
Confirm JSON_SCHEMA_VALID function availabilityConnect to MariaDB and run 'SHOW CREATE FUNCTION JSON_SCHEMA_VALID\G' or attempt to use the function with a simple test query like 'SELECT JSON_SCHEMA_VALID('{"type":"object"}', '{}');'Affected if The function exists and executes without error (function is available to authenticated users)
-
Verify authenticated database access scopeReview which database users have access and can execute the JSON_SCHEMA_VALID function by checking grants with 'SHOW GRANTS FOR <user>;'Affected if Untrusted or low-privilege authenticated users have access to execute the JSON_SCHEMA_VALID function
You are affected if your MariaDB version falls within 11.4.1-11.4.9, 11.8.1-11.8.5, or 12.1.2 AND the JSON_SCHEMA_VALID function is accessible to authenticated users in your environment.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped11.4.1011.8.6
Upgrade MariaDB to version 11.4.10, 11.8.6, or 12.2.2 or later. If immediate upgrade is not possible, restrict JSON_SCHEMA_VALID() access to trusted users only.
MariaDB 11.4.10, 11.8.6, or 12.2.2 (depending on which branch you are on)
- 1. Identify the current MariaDB version by running: SELECT VERSION();
- 2. For MariaDB 11.4.x (versions 11.4.1 to 11.4.9): Upgrade to MariaDB 11.4.10 or later
- 3. For MariaDB 11.8.x (versions 11.8.1 to 11.8.5): Upgrade to MariaDB 11.8.6 or later
- 4. For MariaDB 12.1.2: Upgrade to MariaDB 12.2.2 or later (or migrate to 11.4.10+/11.8.6+ if 12.x is not required)
- 5. Verify the upgrade by running: SELECT VERSION(); to confirm the new version is no longer vulnerable
- 6. Test the JSON_SCHEMA_VALID() function in a non-production environment before deploying the upgrade to production
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in MariaDB
Scoped from the published advisory
- Consultation4.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32710 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-32710 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data