CVE-2026-44172

CRITICALNVD 9.19.1—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.1 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 54% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Trending — 3 sources updated this week
9.1EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 9.1Exploit: None knownExposed: 0

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.1(medium)
EG Risk
56(Track)
EG Risk 56/100SSVC: Track

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
Severity91% × 45%
Exploitation1% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
46%
KEV
Not listed

Published

June 12, 2026

Last Modified

July 30, 2026

Advisory Details (13)

Auto-updated Aug 1, 2026
Patch available. Sources: github, redhat.
redhat Patch Available

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44172.json
redhat Patch Available

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
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-44172
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.0 Extended Update Support.

https://access.redhat.com/errata/RHSA-2026:47772
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:43505
redhat Patch Available
https://access.redhat.com/errata/RHSA-2026:30135
generic

[CONC-819] mysql_real_escape_string incorrectly handles big5 - Jira

https://jira.mariadb.org/browse/CONC-819
github Patch Available

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

https://github.com/MariaDB/server/security/advisories/GHSA-pv9p-5w55-55jm
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:33482
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:33481
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:33464
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:33412
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

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

Vendor Advisories for CVE-2026-44172(3)

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

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumariadb-test-data (1:11.8.6-5ubuntu0.1) @ resolute2026-08-25ubuntu
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:11.8-9080020260612104015.rhel92026-06-30redhat
redhatmariadb:10.11-8100020260616102001.489197e62026-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 rangeFixed inDependents
mariadb—10.11.17-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.11-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.11-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.11-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.8.7-r0—
Debian:12(1)
PackageVulnerable rangeFixed inDependents
mariadb1:10.11.11-0+deb12u1 ... 1:10.11.9-0+deb12u1 (21 versions)1:10.11.18-0+deb12u1—
Debian:13(1)
PackageVulnerable rangeFixed inDependents
mariadb1:11.8.2-1 ... 1:11.8.8-1 (19 versions)——
Debian:14(1)
PackageVulnerable rangeFixed inDependents
mariadb1:11.8.2-1 ... 1:11.8.6-6 (15 versions)1:11.8.8-1—
PyPI(1)
PackageVulnerable rangeFixed inDependents
mariadb0.9.52 ... 2.0.0rc2 (42 versions)——

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 23× in last 7d / 169× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

Showing the most recent 100 of 320 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44172?
CVE-2026-44172 is a critical vulnerability 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 CVE-2026-44172 disclosed?
CVE-2026-44172 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on July 30, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44172 actively exploited?
CVE-2026-44172 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 54.2% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44172, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

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.

Start Free Scan →Browse All CVEs