CVE-2026-44172
Mariadb SQL injection
- Published12 Jun 2026
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.
CVSS 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
No fixed version is recorded in the NVD data. Check the vendor advisory for the latest guidance.
References
- https://access.redhat.com/errata/RHSA-2026:30135
- https://access.redhat.com/errata/RHSA-2026:43505
- https://access.redhat.com/errata/RHSA-2026:47772
- https://access.redhat.com/errata/RHSA-2026:68567
- https://access.redhat.com/security/cve/CVE-2026-44172
- https://bugzilla.redhat.com/show_bug.cgi?id=2488459
- https://github.com/MariaDB/server/security/advisories/GHSA-pv9p-5w55-55jm
- https://jira.mariadb.org/browse/CONC-819
- https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44172.json
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-44172 being actively exploited?
CVE-2026-44172 is not in the CISA KEV catalog. Its EPSS exploit probability is 1.04%.
How severe is CVE-2026-44172?
CVE-2026-44172 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 1.04% probability of exploitation.
Which products are affected by CVE-2026-44172?
Affected products include Mariadb, Redhat Enterprise Linux.
How do I fix CVE-2026-44172?
Apply the vendor's patch or advisory guidance, then verify no affected versions remain across your devices.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-44172 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.