# CVE-2026-107821: MariaDB: insufficient validation of binary frm data when opening a table > An attacker with file write access can cause memory corruption in MariaDB via crafted FRM files, leading to crashes or code execution. - **Severity:** High 8.0 (`CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:C/C:H/I:H/A:H`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 9 Oct 2026 - **Updated:** 9 Oct 2026 - **Also known as:** BELL-CVE-2026-107821, BIT-mariadb-2026-107821, BIT-mariadb-min-2026-107821, BIT-mysql-client-2026-107821, DEBIAN-CVE-2026-107821, ECHO-29a2-0126-be03, GHSA-c4gx-34mg-95q5, MINI-5pw4-vfmq-w4fr, MINI-8qjv-hmvc-558q, MINI-cw5m-rj8q-9597, MINI-hfmm-7gw3-8jcv, MINI-mxc4-rw6p-xwm8, MINI-qm7v-cv29-rcjw, ROOT-OS-DEBIAN-12-CVE-2026-107821, ROOT-OS-DEBIAN-13-CVE-2026-107821, UBUNTU-CVE-2026-107821 ## What is CVE-2026-107821? CVE-2026-107821 is a high-severity memory corruption vulnerability in Mariadb Mariadb, published on 9 Oct 2026. An attacker needs administrator access to exploit it, 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, MariaDB insufficiently validated counts, offsets, lengths, and field boundaries in FRM metadata while opening binary FRM files. An attacker able to place a crafted FRM file in the data directory could trigger out-of-bounds reads or writes, crash the server, or potentially execute code. 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-1285 (Improper Validation of Specified Index, Position, or Offset in Input) ## Which versions are affected by CVE-2026-107821? 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-107821? 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-107821 being exploited? There is no known exploitation of CVE-2026-107821 in the wild and no public exploit code. Public exploit code: - The MariaDB 13.1.0 RCE LAB is a testing environment designed to validate an exploit chain that combines an OOB Read vulnerability in the share->field pointer array with multiple additional vulnerabilities, ultimately achieving arbitrary code execution with mysql privileges. (github_poc): https://github.com/pinebudweiser/CVE-2026-107821-PoC ## 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-107821 and fix it if it is affected. What it is: CVE-2026-107821 is a high-severity memory corruption vulnerability in Mariadb Mariadb, published on 9 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-107821 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-107821/ (Markdown: https://insights.sbomify.com/CVE-2026-107821/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107821 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107821 - OSV: https://osv.dev/vulnerability/CVE-2026-107821 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107821/ Summaries are generated and may contain mistakes; the official description above is the record.