CVE-2026-44169

MEDIUMPre-NVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 85% 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, secondary
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0.3%CVSS: 4.3Exploit: None knownExposed services: Not assessed

A fix is available — apply it.

MariaDB server is a community developed fork of MySQL server. From versions 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1, a user getting EXECUTE access to a stored routine via a role, could see the routine definition even without SHOW CREATE ROUTINE privilege. This issue has been patched in versions 11.4.11, 11.8.7, and 12.3.2.

CVSS v3
4.3
EG Score
4.3MEDIUMmedium confidence
EG Risk
19
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
EPSS PROB
0.3%
EPSS %ILE
17th
KEV
Not listed

Published

June 12, 2026

Last Modified

June 17, 2026

Advisory Details (2)

Auto-updated Jun 18, 2026
Patch available. Sources: github.
generic

[MDEV-39288] SHOW CREATE ROUTINE does not apply to roles - Jira

https://jira.mariadb.org/browse/MDEV-39288
githubMentions a patch (unverified)

Authorization bypass in role-based routine-level privilege check exposes stored routine definitions · Advisory · MariaDB/server · GitHub

https://github.com/MariaDB/server/security/advisories/GHSA-22xq-vq3f-87x2

Vendor Advisories for CVE-2026-44169(4)

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

Patch Availability(8)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumariadb-test-data (1:11.8.6-5ubuntu0.1) @ resolute2026-09-14ubuntu
redhatmariadb:10.11-9080020260612103452.rhel92026-06-30redhat
redhatmariadb11.8-3:11.8.8-1.el10_22026-06-30redhat
redhatmariadb:10.11-8100020260616102001.489197e62026-06-30redhat
redhatmariadb:11.8-9080020260612104015.rhel92026-06-30redhat
redhatmariadb10.11-3:10.11.18-1.el10_22026-06-29redhat
redhatmariadb10-11-main-10.11.18-1.hum12026-06-10redhat
redhatmariadb11-8-main-11.8.8-1.hum12026-06-10redhat

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

(8 across 8 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 11.4.1 up to 10.11.17-r0: fixed in 10.11.17-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 11.4.1 up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 11.4.1 up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 11.4.1 up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 11.4.1 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:11.8.9+ds-4 (57 versions)
  • every version on: no fix on record
—
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
—

Weakness Classification(1)

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

Additional Vendor Advisories

(4)

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

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

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

Frequently asked(5)

What is CVE-2026-44169?
CVE-2026-44169 is a medium vulnerability published on June 12, 2026. MariaDB server is a community developed fork of MySQL server. From versions 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1, a user getting EXECUTE access to a stored routine via a role, could see the routine definition even without SHOW CREATE ROUTINE privilege. This issue has been…
When was CVE-2026-44169 disclosed?
CVE-2026-44169 was first published on June 12, 2026, with the most recent update on June 17, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44169 actively exploited?
CVE-2026-44169 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.3% probability of exploitation in the next 30 days (17th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44169?
CVE-2026-44169 has a CVSS base score of 4.3 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2026-44169?
A fix for CVE-2026-44169 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44169 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-44169

Explore →

Is Your Infrastructure Affected by CVE-2026-44169?

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

Book a Demo →Browse All CVEs