# CVE-2026-44172: MariaDB: mysql_real_escape_string() incorrectly handled big5 > Attackers can execute SQL injection attacks in MariaDB when using big5 character set with unvalidated input, bypassing escape functions. - **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** Not needed - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 12 Jun 2026 - **Updated:** 17 Sep 2026 - **Also known as:** ALPINE-CVE-2026-44172, ALSA-2026:43505, ALSA-2026:75673, ALSA-2026:75674, BELL-CVE-2026-44172, BIT-mariadb-2026-44172, BIT-mariadb-min-2026-44172, BIT-mysql-client-2026-44172, CLSA-2026-1791795699, CLSA-2026-1791796759, DEBIAN-CVE-2026-44172, ECHO-6ea8-c8b9-7dda, GHSA-pv9p-5w55-55jm, OESA-2026-3197, PYSEC-2026-217, RHSA-2026:30135, RHSA-2026:43505, RHSA-2026:47772, RHSA-2026:68567, RHSA-2026:75673, RHSA-2026:75674, RHSA-2026:83079, RHSA-2026:83080, RHSA-2026:83517, RHSA-2026:83518, RHSA-2026:83519, RHSA-2026:83608, RLSA-2026:43505, RLSA-2026:75673, RLSA-2026:75674, ROOT-OS-DEBIAN-13-CVE-2026-44172, SUSE-SU-2026:22844-1, SUSE-SU-2026:3110-1, SUSE-SU-2026:3134-1, SUSE-SU-2026:3135-1, UBUNTU-CVE-2026-44172, openSUSE-SU-2026:11721-1, openSUSE-SU-2026:21409-1 ## What is CVE-2026-44172? CVE-2026-44172 is a medium-severity SQL injection vulnerability in Mariadb Mariadb, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. ### Official description MariaDB server is a community developed fork of MySQL server. In versions 3.3.18 and 3.4.8, an application that was taking non-validated user input, escaping it with mysql_real_escape_string() and sending it to the database using text protocol and big5 character set was vulnerable to SQL injections, even though mysql_real_escape_string() was supposed to prevent them. This issue has been patched in versions 3.3.19 and 3.4.9. Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command) ## Which versions are affected by CVE-2026-44172? 4 open source packages ship an affected version, including mariadb, mariadb-min and mysql-client. It affects 2 products. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `mariadb` | Bitnami | From 3.3.18 | 10.4.34 | | `mariadb` | PyPI | All versions to 3.3.18 | None | | `mariadb-min` | Bitnami | From 3.3.18 | 10.6.23 | | `mysql-client` | Bitnami | From 3.3.18 | 10.6.17 | | `mariadb-connector-c` | AlmaLinux:10 | All versions | 3.4.4-2.el10_2 | | `mariadb-connector-c-config` | AlmaLinux:10 | All versions | 3.4.4-2.el10_2 | | `mariadb-connector-c-devel` | AlmaLinux:10 | All versions | 3.4.4-2.el10_2 | | `mariadb-connector-c-doc` | AlmaLinux:10 | All versions | 3.4.4-2.el10_2 | | `mariadb-connector-c-test` | AlmaLinux:10 | All versions | 3.4.4-2.el10_2 | | `mariadb-connector-c` | AlmaLinux:8 | All versions | 3.1.11-3.el8_10 | | `mariadb-connector-c-config` | AlmaLinux:8 | All versions | 3.1.11-3.el8_10 | | `mariadb-connector-c-devel` | AlmaLinux:8 | All versions | 3.1.11-3.el8_10 | | `mariadb-connector-c` | AlmaLinux:9 | All versions | 3.2.6-2.el9_8 | | `mariadb-connector-c-config` | AlmaLinux:9 | All versions | 3.2.6-2.el9_8 | | `mariadb-connector-c-devel` | AlmaLinux:9 | All versions | 3.2.6-2.el9_8 | | `mariadb-connector-c-doc` | AlmaLinux:9 | All versions | 3.2.6-2.el9_8 | | `mariadb-connector-c-test` | AlmaLinux:9 | All versions | 3.2.6-2.el9_8 | | `mariadb-connector-c` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c-config` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c-debugsource` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c-devel` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c-devel-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c-doc` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c-test` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c-test-debuginfo` | Red Hat:enterprise_linux:10.2 | All versions | 0:3.4.4-2.el10_2 | | `mariadb-connector-c` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.1.11-3.el8_10 | | `mariadb-connector-c-config` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.1.11-3.el8_10 | | `mariadb-connector-c-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.1.11-3.el8_10 | | `mariadb-connector-c-debugsource` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.1.11-3.el8_10 | | `mariadb-connector-c-devel` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.1.11-3.el8_10 | | `mariadb-connector-c-devel-debuginfo` | Red Hat:enterprise_linux:8::appstream | All versions | 0:3.1.11-3.el8_10 | | `mariadb-connector-c` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.6-2.el9_8 | | `mariadb-connector-c-config` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.6-2.el9_8 | | `mariadb-connector-c-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.6-2.el9_8 | | `mariadb-connector-c-debugsource` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.6-2.el9_8 | | `mariadb-connector-c-devel` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.6-2.el9_8 | | `mariadb-connector-c-devel-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.6-2.el9_8 | | `mariadb-connector-c-test-debuginfo` | Red Hat:enterprise_linux:9::appstream | All versions | 0:3.2.6-2.el9_8 | | `mariadb-connector-c-debuginfo` | Red Hat:enterprise_linux:9::crb | All versions | 0:3.2.6-2.el9_8 | Products: Mariadb Mariadb, Redhat Enterprise Linux. ## How do I fix CVE-2026-44172? Upgrade mariadb to 10.4.34 or later. ## Is CVE-2026-44172 being exploited? There is no known exploitation of CVE-2026-44172 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-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-44172 and fix it if it is affected. What it is: CVE-2026-44172 is a medium-severity SQL injection vulnerability in Mariadb Mariadb, published on 12 Jun 2026. An attacker can exploit it over the internet without logging in, with no action from the victim. Exploitation: There is no known exploitation of CVE-2026-44172 in the wild and no public exploit code. Affected packages and fixed versions: - mariadb (Bitnami): affected from 3.3.18; fixed in 10.4.34 - mariadb (PyPI): affected all versions up to 3.3.18; no fix listed - mariadb-min (Bitnami): affected from 3.3.18; fixed in 10.6.23 - mysql-client (Bitnami): affected from 3.3.18; fixed in 10.6.17 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-44172/ (Markdown: https://insights.sbomify.com/CVE-2026-44172/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44172 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44172 - OSV: https://osv.dev/vulnerability/CVE-2026-44172 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-44172/ Summaries are generated and may contain mistakes; the official description above is the record.