PatchSiren cyber security CVE debrief
CVE-2026-44172 MariaDB CVE debrief
A vulnerability in MariaDB server versions 3.3.18 and 3.4.8 allows for SQL injections when 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. This issue has been patched in versions 3.3.19 and 3.4.9. The vulnerability exists due to the insufficient escaping of user input, which can be exploited by an attacker to inject malicious SQL code. Defenders should prioritize patching to versions 3.3.19 or 3.4.9 and validate user input to prevent potential attacks.
- Vendor
- MariaDB
- Product
- server
- CVSS
- MEDIUM 6.9
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-06-12
- Original CVE updated
- 2026-09-17
- Advisory published
- 2026-06-12
- Advisory updated
- 2026-09-17
Who should care
Defenders managing MariaDB server instances, especially those exposed to untrusted user input, should prioritize patching and validating user input. This includes database administrators, security teams, and IT personnel responsible for maintaining MariaDB server instances. Additionally, developers who use MariaDB server in their applications should also take action to validate user input and prevent SQL injections.
Why it matters
CVE-2026-44172 is a SQL injection vulnerability in MariaDB server versions 3.3.18 and 3.4.8. Defenders should prioritize patching to versions 3.3.19 or 3.4.9 and validate user input to prevent potential attacks.
- Potential SQL injection attacks
- Data integrity and confidentiality risks
- Need for patching and input validation
Technical summary
The vulnerability exists in MariaDB server versions 3.3.18 and 3.4.8, allowing SQL injections when using mysql_real_escape_string() with text protocol and big5 character set. Patching to versions 3.3.19 or 3.4.9 mitigates the issue. The vulnerability is caused by the insufficient escaping of user input, which can be exploited by an attacker to inject malicious SQL code. Defenders should prioritize patching and validating user input to prevent potential attacks. The vulnerability has been publicly disclosed and defenders should take immediate action to patch vulnerable instances.
Defensive priority
Defenders should prioritize patching vulnerable MariaDB server instances, especially those exposed to untrusted user input.
Recommended defensive actions
- Patch MariaDB server instances to versions 3.3.19 or 3.4.9
- Validate and sanitize user input to prevent SQL injections
- Review database configurations and access controls
- Implement monitoring and detection mechanisms to identify potential attacks
- Conduct regular security audits and vulnerability assessments
- Review and update incident response plans to address potential SQL injection attacks
- Verify the integrity of data stored in the database
Evidence notes
The vulnerability exists in MariaDB server versions 3.3.18 and 3.4.8. The issue allows for SQL injections under specific conditions. Patching to versions 3.3.19 or 3.4.9 is recommended. Evidence is based on the official CVE record and NVD vulnerability detail page. The vulnerability has been publicly disclosed and defenders should take immediate action to patch vulnerable instances.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-44172 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-44172
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-44172 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-44172
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://github.com/MariaDB/server/security/advisories/GHSA-pv9p-5w55-55jm
[email protected] - Mitigation, Vendor Advisory
-
Source reference
Unverified legacy reference
URL: https://jira.mariadb.org/browse/CONC-819
[email protected] - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:30135
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:43505
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:47772
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/errata/RHSA-2026:68567
0b0ca135-0b70-47e7-9f44-1890c2a1c46c
-
Source reference
Unverified legacy reference
URL: https://access.redhat.com/security/cve/CVE-2026-44172
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
-
Source reference
Unverified legacy reference
URL: https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44172.json
0b0ca135-0b70-47e7-9f44-1890c2a1c46c - Third Party Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.