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 94% 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
Trending — 3 sources updated this week
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0

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.3(medium)
EG Risk
19(Track)
EG Risk 19/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
Severity43% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
5.7%
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
github Patch Available

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 / EcosystemFixed in / PatchReleasedSource
ubuntumariadb-test-data (1:11.8.6-5ubuntu0.1) @ resolute2026-07-16ubuntu
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.

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 9× in last 7d / 53× 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.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:14 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 02:29 UTCEPSS rescore
  8. 2026-07-18 10:04 UTCEPSS rescore
  9. 2026-07-17 06:15 UTCVendor advisory
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-16 04:22 UTCVendor advisory
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 04:01 UTCVendor advisory
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-14 03:59 UTCVendor advisory
  16. 2026-07-13 22:30 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 03:57 UTCVendor advisory
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-12 03:52 UTCVendor advisory
  21. 2026-07-11 08:27 UTCEPSS rescore
  22. 2026-07-11 03:34 UTCVendor advisory
  23. 2026-07-10 03:26 UTCVendor advisory
  24. 2026-07-09 19:10 UTCEPSS rescore
  25. 2026-07-09 02:28 UTCVendor advisory
Show 44 more
  1. 2026-07-08 15:16 UTCEPSS rescore
  2. 2026-07-08 01:22 UTCVendor advisory
  3. 2026-07-07 13:46 UTCEPSS rescore
  4. 2026-07-07 01:06 UTCVendor advisory
  5. 2026-07-06 16:27 UTCEPSS rescore
  6. 2026-07-06 02:23 UTCEPSS rescore
  7. 2026-07-05 21:43 UTCVendor advisory
  8. 2026-07-05 02:30 UTCEPSS rescore
  9. 2026-07-04 21:41 UTCVendor advisory
  10. 2026-07-04 06:31 UTCEPSS rescore
  11. 2026-07-03 21:05 UTCVendor advisory
  12. 2026-07-02 21:03 UTCVendor advisory
  13. 2026-07-01 21:01 UTCVendor advisory
  14. 2026-07-01 15:07 UTCEPSS rescore
  15. 2026-06-30 23:22 UTCEPSS rescore
  16. 2026-06-30 20:58 UTCVendor advisory
  17. 2026-06-29 20:56 UTCVendor advisory
  18. 2026-06-29 14:06 UTCEPSS rescore
  19. 2026-06-28 20:55 UTCVendor advisory
  20. 2026-06-28 14:07 UTCEPSS rescore
  21. 2026-06-28 04:56 UTCEPSS rescore
  22. 2026-06-27 20:53 UTCVendor advisory
  23. 2026-06-27 03:08 UTCEPSS rescore
  24. 2026-06-26 20:51 UTCVendor advisory
  25. 2026-06-25 20:50 UTCVendor advisory
  26. 2026-06-25 13:49 UTCEPSS rescore
  27. 2026-06-25 13:49 UTCEPSS rescore
  28. 2026-06-24 14:05 UTCEPSS rescore
  29. 2026-06-23 21:33 UTCEPSS rescore
  30. 2026-06-22 14:25 UTCEPSS rescore
  31. 2026-06-22 14:25 UTCEPSS rescore
  32. 2026-06-21 14:56 UTCEPSS rescore
  33. 2026-06-21 14:56 UTCEPSS rescore
  34. 2026-06-21 01:59 UTCEPSS rescore
  35. 2026-06-19 19:25 UTCEPSS rescore
  36. 2026-06-18 17:52 UTCEPSS rescore
  37. 2026-06-18 17:52 UTCEPSS rescore
  38. 2026-06-17 17:53 UTCEPSS rescore
  39. 2026-06-16 17:52 UTCEPSS rescore
  40. 2026-06-15 17:49 UTCEPSS rescore
  41. 2026-06-13 23:00 UTCEPSS rescore
  42. 2026-06-12 23:12 UTCEPSS rescore
  43. 2026-06-12 20:14 UTCEG score recompute
  44. 2026-06-12 20:13 UTCNVD updatefirst tracked

Related CVEs(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 in the National Vulnerability Database 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 5.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44169?
CVE-2026-44169 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-44169?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44169, 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

Explore the affected products and dependency analysis for 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.

Start Free Scan →Browse All CVEs