dbcve.org
MariaDBDatabase / datastore

CVE-2026-44172

CRITICAL · 9.1 CVSS v3.1 Published 2026-06-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
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.

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 confidence

MariaDB versions 3.3.18 and 3.4.8 contain a SQL injection vulnerability when using the big5 character set with mysql_real_escape_string(). The escaping function can be bypassed due to character set handling, allowing attackers to inject malicious SQL through user input that was supposedly sanitized.

MitigationUpgrade MariaDB server to version 3.3.19 or 3.4.9 to apply the patch. Additionally, use parameterized queries (prepared statements) instead of escaped strings as a defense-in-depth measure.

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
Affected:= 3.3.18= 3.4.8
Enterprise LinuxOperating system
Affected:= 10.0

CVSS 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
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Check MariaDB server version
    Run 'SELECT VERSION();' on the database server or execute 'mysqld --version' from command line
    Affected if Version is exactly 3.3.18 or 3.4.8
  2. Identify big5 character set usage
    Execute 'SHOW VARIABLES LIKE 'character_set_%';' and inspect character_set_connection, character_set_client, and character_set_results values
    Affected if Any of these variables are set to 'big5'
  3. Confirm text protocol is active
    Text protocol is the default for MariaDB connections. Check application connection strings or session variables for protocol settings. Prepared statements use binary protocol and are not affected
    Affected if Connections use default text protocol (not prepared statements)
  4. Locate mysql_real_escape_string usage
    Audit application source code for calls to mysql_real_escape_string or mysqli_real_escape_string, specifically where the connection character set is configured as big5
    Affected if Application code uses mysql_real_escape_string with big5-configured connections

Environment is affected if MariaDB version is 3.3.18 or 3.4.8 AND applications use big5 character set with text protocol while relying on mysql_real_escape_string for input sanitization

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade MariaDB server to version 3.3.19 or 3.4.9 to apply the patch. Additionally, use parameterized queries (prepared statements) instead of escaped strings as a defense-in-depth measure.

Recommended fix High confidence

MariaDB 3.3.19 or 3.4.9 (or latest stable 3.3.x/3.4.x release)

  1. 1. Identify the current MariaDB server version using: `mysql --version` or `SELECT VERSION();`
  2. 2. Stop the MariaDB service before upgrading: `systemctl stop mariadb` or `service mysql stop`
  3. 3. Upgrade MariaDB to version 3.3.19 or 3.4.9 (or the latest stable release in that branch) using your system's package manager (e.g., `yum update mariadb-server`, `apt install mariadb-server`, or `zypper update mariadb`)
  4. 4. Start the MariaDB service after upgrade: `systemctl start mariadb` or `service mysql start`
  5. 5. Verify the new version is installed: `mysql --version` or `SELECT VERSION();`
  6. 6. Review the MariaDB release notes for version 3.3.19/3.4.9 for any additional post-upgrade actions required
Caveat Check MariaDB release notes for any migration or compatibility notes between versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in MariaDB Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing12.0 h
  • Review / QA4.0 h
28.0 hours of engineering $4,760
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-44172 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-44172 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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