# CVE-2026-85746: MariaDB: Out-of-bound buffer write on in `ST_AsText` of nested GeometryCollections

> A low-privileged remote attacker can trigger an out-of-bounds write in MariaDB's ST_AsText function via crafted GIS objects, potentially leading to code execution.

- **Severity:** Critical 9.9 (`CVSS:3.1/AV:N/AC:L/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:** 16 Oct 2026
- **Updated:** 16 Oct 2026
- **Also known as:** BIT-mariadb-2026-85746, BIT-mariadb-min-2026-85746, BIT-mysql-client-2026-85746, DEBIAN-CVE-2026-85746, ECHO-131b-d049-cafb, GHSA-8fvj-c57c-pggx, ROOT-OS-DEBIAN-12-CVE-2026-85746, ROOT-OS-DEBIAN-13-CVE-2026-85746, UBUNTU-CVE-2026-85746

## What is CVE-2026-85746?

CVE-2026-85746 is a critical memory corruption vulnerability in Mariadb Mariadb, published on 16 Oct 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. From 10.6.1 until 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2, ST_AsText can write beyond an allocated output buffer when converting deeply nested GeometryCollections because recursive WKT serialization does not account for bytes consumed or reserve sufficient space. A low-privileged remote attacker can submit a specially crafted GIS object to corrupt memory and potentially achieve code execution when combined with another vulnerability. This issue is fixed in versions 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, and 13.0.2.

Weakness: CWE-787 (Out-of-bounds Write)

## Which versions are affected by CVE-2026-85746?

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 10.6.1 | 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 |
| `mariadb-min` | Bitnami | From 10.6.1 | 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 |
| `mysql-client` | Bitnami | From 10.6.1 | 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2 |

Products: Mariadb Mariadb.

## How do I fix CVE-2026-85746?

Upgrade mariadb to a fixed version for your release line: 10.6.28, 10.11.19, 11.4.13 or 11.8.9.

## Is CVE-2026-85746 being exploited?

There is no known exploitation of CVE-2026-85746 in the wild and no public exploit code.

## 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-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)
- [CVE-2026-97380](https://insights.sbomify.com/CVE-2026-97380/): MariaDB: GRANT PROXY with empty password incorrectly checks grantor's privileges (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-85746 and fix it if it is affected.

What it is: CVE-2026-85746 is a critical memory corruption vulnerability in Mariadb Mariadb, published on 16 Oct 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-85746 in the wild and no public exploit code.

Affected packages and fixed versions:
- mariadb (Bitnami): affected from 10.6.1; fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
- mariadb-min (Bitnami): affected from 10.6.1; fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.2
- mysql-client (Bitnami): affected from 10.6.1; fixed in 10.6.28, 10.11.19, 11.4.13, 11.8.9, 12.3.3, 13.0.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-85746/ (Markdown: https://insights.sbomify.com/CVE-2026-85746/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-85746
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-85746
- OSV: https://osv.dev/vulnerability/CVE-2026-85746

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-85746/
Summaries are generated and may contain mistakes; the official description above is the record.