CVE-2026-44172

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 66% 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 — 5 sources updated this week
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.8Exploit: NoneExposed: 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.8
EG Score
9.8(medium)
EPSS
33.8%
KEV
Not listed

Published

June 12, 2026

Last Modified

July 10, 2026

Advisory Details (10)

Auto-updated Jul 3, 2026
Patch available. Sources: github, redhat.
redhat

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()

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

Patch Availability(6)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatmariadb:10.11-9080020260612103452.rhel92026-06-30redhat
redhatmariadb:10.11-8100020260616102001.489197e62026-06-30redhat
redhatmariadb11.8-3:11.8.8-1.el10_22026-06-30redhat
redhatmariadb:11.8-9080020260612104015.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

(1 across 1 ecosystem)
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

(1)

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 67× in last 7d / 199× 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 199 total refreshes for this CVE.

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

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 10, 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 33.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44172?
CVE-2026-44172 has a CVSS v3 base score of 9.8 (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.