CVE-2026-44172

CRITICALNVD 9.19.1
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to NVD's CVSS score.

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 1.0% (63rd percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from NVD CVSS v3
Sources: EPSS, NVD CVSS v3
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixRemediate within your standard update timelines at low or medium mission impact and sooner than that at high (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1.0%CVSS: 9.1Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

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 v3
9.1
EG Score
9.1CRITICALmedium confidence
EG Risk
56
EG Risk 56/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity91% × 45%
The EG Score, 9.1 of 10.
Exploitation1.0% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability100% × 15%
CISA's SSVC Automatable value: yes (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Attend at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
EPSS PROB
1.0%
EPSS %ILE
63rd
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Attend at high (mission-essential systems).

A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.

Exploitation none (CISA Vulnrichment) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; 60 days if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable yes (CISA Vulnrichment) · Technical impact partial (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

June 12, 2026

Last Modified

September 17, 2026

Advisory Details (13)

Auto-updated Sep 16, 2026
Patch available. Sources: github, redhat.
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44172.json
Red HatMentions a patch (unverified)

2488459 – (CVE-2026-44172) CVE-2026-44172 mariadb: MariaDB server: SQL injection vulnerability via improper handling of big5 character set with mysql_real_escape_string()

Affected: Red Hat Enterprise Linux 10

https://bugzilla.redhat.com/show_bug.cgi?id=2488459
Red HatMentions a patch (unverified)

CVE-2026-44172 - Red Hat Customer Portal

Affected: Red Hat Enterprise Linux 8 or OpenShift Container Platform 4, is affected by this vulnerability and a fix may be released to a

https://access.redhat.com/security/cve/CVE-2026-44172
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:47772
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:43505
Red HatMentions a patch (unverified)
https://access.redhat.com/errata/RHSA-2026:30135
Web page

[CONC-819] mysql_real_escape_string incorrectly handles big5 - Jira

https://jira.mariadb.org/browse/CONC-819
GitHub advisoryMentions a patch (unverified)

mysql_real_escape_string() incorrectly handled big5 · Advisory · MariaDB/server · GitHub

https://github.com/MariaDB/server/security/advisories/GHSA-pv9p-5w55-55jm
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:33482
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:33481
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:33464
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:33412
Red HatMentions a patch (unverified)

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:33093

Vendor Advisories for CVE-2026-44172(6)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Patch Availability(12)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumariadb-test-data (1:11.8.6-5ubuntu0.1) @ resolute2026-10-12ubuntu
redhatmariadb-connector-c-0:3.1.11-3.el8_102026-10-05redhat
redhatmariadb-connector-c-0:3.2.6-2.el9_82026-10-05redhat
redhatmariadb-connector-c-0:3.4.9-1.el9ai2026-09-17redhat
redhatmariadb-connector-c-0:3.4.4-1.el10_0.12026-07-29redhat
redhatmariadb-connector-c-0:3.4.4-2.el10_22026-07-22redhat
redhatmariadb:10.11-8100020260616102001.489197e62026-06-30redhat
redhatmariadb:11.8-9080020260612104015.rhel92026-06-30redhat
redhatmariadb11.8-3:11.8.8-1.el10_22026-06-30redhat
redhatmariadb:10.11-9080020260612103452.rhel92026-06-30redhat
redhatmariadb10.11-3:10.11.18-1.el10_22026-06-29redhat
redhatmariadb-connector-c-main-3.4.9-1.hum12026-06-25redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

Affected Packages

(9 across 9 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • every version up to 10.11.17-r0: fixed in 10.11.17-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • every version up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • every version up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • every version up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • every version up to 11.8.7-r0: fixed in 11.8.7-r0
—
Debian:12(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb1:10.11.11-0+deb12u1 ... 1:10.11.9-0+deb12u1 (21 versions)
  • every version up to 1:10.11.18-0+deb12u1: fixed in 1:10.11.18-0+deb12u1
—
Debian:13(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb1:11.8.2-1 ... 1:11.8.9+ds-4 (23 versions)
  • every version on: no fix on record
—
Debian:14(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb1:11.8.2-1 ... 1:11.8.6-6 (15 versions)
  • every version up to 1:11.8.8-1: fixed in 1:11.8.8-1
—
PyPI(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb0.9.52 ... 2.0.0rc2 (42 versions)
  • every version through 3.3.18: no fix on record
  • every version through 3.4.8: no fix on record
—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Additional Vendor Advisories

(6)

Vendors that published advisories for this CVE beyond the curated set above. Broader coverage but minimal per-row detail — click through for the original advisory.

Data Freshness Timeline

(refreshed 17× in last 7d / 34× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 373 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 273 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-14 16:33 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  2. 2026-10-14 02:10 UTCEG score recompute
  3. 2026-10-14 02:10 UTCVendor advisory
  4. 2026-10-13 16:34 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  5. 2026-10-12 22:30 UTCEG score recompute
  6. 2026-10-12 22:30 UTCVendor advisory
  7. 2026-10-12 16:34 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  8. 2026-10-12 16:05 UTCEG score recompute
  9. 2026-10-12 07:51 UTCVendor advisory
  10. 2026-10-11 19:47 UTCEG score recompute
  11. 2026-10-11 17:02 UTCEG score recompute
  12. 2026-10-11 14:27 UTCEG score recompute
  13. 2026-10-11 13:48 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  14. 2026-10-10 20:00 UTCEPSS rescoreEPSS 1.0% · 63rd percentile
  15. 2026-10-09 20:07 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  16. 2026-10-08 17:12 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  17. 2026-10-07 23:48 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  18. 2026-10-06 15:18 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  19. 2026-10-05 17:43 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  20. 2026-10-04 23:22 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  21. 2026-10-03 14:25 UTCEPSS rescoreEPSS 1.0% · 62nd percentile
  22. 2026-10-01 19:50 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  23. 2026-09-30 15:03 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  24. 2026-09-27 13:48 UTCEPSS rescoreEPSS 1.0% · 61st percentile
  25. 2026-09-26 15:58 UTCEPSS rescoreEPSS 1.0% · 61st percentile
Show 75 more
  1. 2026-09-23 17:53 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  2. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  3. 2026-09-18 19:28 UTCEPSS rescoreEPSS 0.7% · 50th percentile
  4. 2026-09-17 19:31 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  5. 2026-09-17 12:20 UTCVendor advisory
  6. 2026-09-17 12:10 UTCEG score recompute
  7. 2026-09-17 12:10 UTCVendor advisory
  8. 2026-09-16 14:08 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  9. 2026-09-16 05:15 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  10. 2026-09-14 08:15 UTCVendor advisory
  11. 2026-09-14 03:59 UTCEG score recompute
  12. 2026-09-14 03:59 UTCVendor advisory
  13. 2026-09-13 16:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  14. 2026-09-12 15:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  15. 2026-09-11 14:53 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  16. 2026-09-11 09:37 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  17. 2026-09-10 09:34 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  18. 2026-09-08 22:00 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  19. 2026-09-07 16:01 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  20. 2026-09-06 13:47 UTCEPSS rescoreEPSS 0.6% · 46th percentile
  21. 2026-09-04 05:06 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  22. 2026-09-02 14:12 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  23. 2026-09-01 13:54 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  24. 2026-08-30 23:41 UTCEG score recompute
  25. 2026-08-30 23:41 UTCVendor advisory
  26. 2026-08-30 19:17 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  27. 2026-08-30 01:22 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  28. 2026-08-28 21:41 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  29. 2026-08-27 14:25 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  30. 2026-08-26 14:46 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  31. 2026-08-25 13:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  32. 2026-08-25 03:55 UTCVendor advisory
  33. 2026-08-24 23:49 UTCEG score recompute
  34. 2026-08-24 23:49 UTCVendor advisory
  35. 2026-08-23 22:29 UTCVendor advisory
  36. 2026-08-23 18:14 UTCVendor advisory
  37. 2026-08-23 14:09 UTCVendor advisory
  38. 2026-08-23 10:00 UTCEG score recompute
  39. 2026-08-23 10:00 UTCVendor advisory
  40. 2026-08-23 00:19 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  41. 2026-08-21 23:49 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  42. 2026-08-21 23:33 UTCVendor advisory
  43. 2026-08-21 19:13 UTCVendor advisory
  44. 2026-08-21 14:52 UTCVendor advisory
  45. 2026-08-21 10:47 UTCVendor advisory
  46. 2026-08-21 06:33 UTCVendor advisory
  47. 2026-08-21 00:38 UTCEG score recompute
  48. 2026-08-21 00:38 UTCVendor advisory
  49. 2026-08-20 22:55 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  50. 2026-08-20 20:32 UTCVendor advisory
  51. 2026-08-20 16:27 UTCVendor advisory
  52. 2026-08-20 08:46 UTCEG score recompute
  53. 2026-08-20 08:46 UTCVendor advisory
  54. 2026-08-19 17:04 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  55. 2026-08-19 13:44 UTCEG score recompute
  56. 2026-08-19 13:44 UTCVendor advisory
  57. 2026-08-18 13:48 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  58. 2026-08-17 15:10 UTCEG score recompute
  59. 2026-08-17 15:10 UTCVendor advisory
  60. 2026-08-17 13:47 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  61. 2026-08-17 11:06 UTCVendor advisory
  62. 2026-08-17 07:00 UTCVendor advisory
  63. 2026-08-17 02:55 UTCVendor advisory
  64. 2026-08-16 22:50 UTCVendor advisory
  65. 2026-08-16 15:56 UTCEG score recompute
  66. 2026-08-16 15:56 UTCVendor advisory
  67. 2026-08-16 14:56 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  68. 2026-08-16 11:51 UTCVendor advisory
  69. 2026-08-16 07:47 UTCVendor advisory
  70. 2026-08-16 03:42 UTCEG score recompute
  71. 2026-08-16 03:42 UTCVendor advisory
  72. 2026-08-16 02:14 UTCEPSS rescoreEPSS 0.6% · 45th percentile
  73. 2026-08-15 23:37 UTCVendor advisory
  74. 2026-08-15 18:42 UTCVendor advisory
  75. 2026-08-15 14:37 UTCVendor advisory

Related CVEs(same product + same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44172?
CVE-2026-44172 is a critical-severity vulnerability; its CVE record was published on June 12, 2026. 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 mysqlrealescapestring() and sending it to the database using text protocol and big5 character set was vulnerable to SQL injections,…
When was the CVE record for CVE-2026-44172 published?
The CVE record for CVE-2026-44172 was published on June 12, 2026. That is the record's publication date; the vulnerability itself may have been made public earlier. EchelonGraph's copy of the record carries a last-modified date of September 17, 2026; the record at its source may have been updated since.
Is CVE-2026-44172 actively exploited?
CVE-2026-44172 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1.0% probability of exploitation in the next 30 days (63rd percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44172?
CVE-2026-44172 has a CVSS v3 base score of 9.1 (NVD).
How do I remediate CVE-2026-44172?
A fix for CVE-2026-44172 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44172 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44172

Explore →

Is Your Infrastructure Affected by CVE-2026-44172?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs