LiveActive security incident?Get immediate response
CVE Record

CVE-2026-44172: MariaDB: mysql_real_escape_string() incorrectly handled big5

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.

CriticalCVSS 9.1Not KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

A narrow but serious SQL injection flaw affects MariaDB deployments using specific versions and Big5 text handling. Applications that trusted mysql_real_escape_string() to make user input safe could still produce unsafe SQL under those conditions. Successful exploitation could expose or alter database data.

Executive priority

Treat as urgent for affected database-backed applications, especially public services. The vulnerable condition is specific, but impact is high because SQL injection can compromise confidentiality and integrity of business data.

Technical view

CVE-2026-44172 is a CWE-89 SQL injection issue in MariaDB server versions 3.3.18 and 3.4.8. The flaw occurs when non-validated user input is escaped with mysql_real_escape_string(), sent using text protocol, and the Big5 character set is in use. Fixed versions are 3.3.19 and 3.4.9.

Likely exposure

Exposure appears limited to applications combining affected MariaDB versions, Big5 character set, text protocol, and mysql_real_escape_string() on user-controlled input. Internet-facing applications with those traits should be prioritized.

Exploitation context

The CVSS is 9.1 with network attack vector, low complexity, no privileges, and no user interaction. The source bundle does not show KEV listing or confirmed active exploitation.

Researcher notes

The evidence supports a precise precondition set: affected MariaDB version, Big5 charset, text protocol, and reliance on mysql_real_escape_string(). Do not generalize exposure to all MariaDB deployments without validating those conditions.

Mitigation direction

  • Upgrade affected MariaDB components to 3.3.19 or 3.4.9 where applicable.
  • Identify applications using mysql_real_escape_string(), text protocol, and Big5 character set.
  • Prefer parameterized queries or prepared statements over manual escaping for user input.
  • Review Red Hat errata for packaged updates if using Red Hat distributions.
  • Validate and constrain user input before database query construction.

Validation and detection

  • Inventory MariaDB versions and confirm none are 3.3.18 or 3.4.8.
  • Search application code for mysql_real_escape_string() and Big5 connection settings.
  • Confirm user-controlled values use prepared statements or equivalent safe query binding.
  • Verify package advisory status against MariaDB and Red Hat records.
  • Review logs for unusual SQL errors around Big5-enabled application paths.
Prepared
Confidence
high
Sources
8

Public sources used

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-44172 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Critical
CVSS
9.1 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

2CVSS vectors
5Timeline events
2ADP providers
12Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: yesTechnical Impact: partial

CVSS vector scores

2 official scores

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
9.1CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N3.95.2redhat-SADP
6.9CVSS 4.0MediumCVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N——GitHub_M

Vulnerability scoring details

Base CVSS 4.0 score

6.9Medium
CVSS 4.0 vector shape for CVE-2026-44172Attack VectorAttack ComplexityAttack RequirementsPrivileges RequiredUser InteractionVS ConfidentialityVS IntegrityVS AvailabilitySS ConfidentialitySS IntegritySS Availability

Vector: 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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Attack Requirements
NonePresent
Privileges Required
NoneLowHigh
User Interaction
NonePassiveActive
VS Confidentiality
HighLowNone
VS Integrity
HighLowNone
VS Availability
HighLowNone
SS Confidentiality
HighLowNone
SS Integrity
HighLowNone
SS Availability
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. ADP timelineredhat-SADP

    Made public.

  3. CVE publishedCVE Program

    The CVE record was published.

  4. ADP timelineredhat-SADP

    Reported to Red Hat.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
redhat-SADPmariadb: MariaDB server: SQL injection vulnerability via improper handling of big5 character set with mysql_real_escape_string()
other:Red Hat severity ratingcvssV3_1
  • 2026-06-12T18:01:33.248Z: Reported to Red Hat.
  • 2026-06-12T17:34:04.487Z: Made public.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
MariaDBserver= 3.3.18, = 3.4.8Listed
Weakness

CWE details

CWE-89

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.