CVE-2026-44173

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under NVD CVSS v3. EPSS exploit probability: 0.6%, top 53% 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
5.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.3Exploit: None knownExposed: 0

A fix is available — apply it.

MariaDB server is a community developed fork of MySQL server. From versions 10.6.1 to before 10.6.26, 10.11.1 to before 10.11.17, 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1, MariaDB allowed SELECT ... INTO OUTFILE and SELECT ... INTO DUMPFILE without verifying the FILE privilege if the FROM clause contained only subqueries. This issue has been patched in versions 10.6.26, 10.11.17, 11.4.11, 11.8.7, and 12.3.2.

CVSS v3
5.3
EG Score
5.3(medium)
EG Risk
24(Track)
EG Risk 24/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
Severity53% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
47%
KEV
Not listed

Published

June 12, 2026

Last Modified

August 3, 2026

Advisory Details (2)

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

[MDEV-39493] FILE privilege isn't checked for derived - Jira

https://jira.mariadb.org/browse/MDEV-39493
github Patch Available

FILE privilege was not checked for subqueries in the FROM clause · Advisory · MariaDB/server · GitHub

Affected: 10.6.26, 10.11.17, 11.4.11, 11.8.7, 12.3.2.

https://github.com/MariaDB/server/security/advisories/GHSA-667j-m53j-wpmc

Patch Availability(9)

Vendor / EcosystemFixed in / PatchReleasedSource
ubuntumariadb-test-data (1:11.8.6-5ubuntu0.1) @ resolute2026-08-20ubuntu
redhatmariadb10.11-3:10.11.18-1.el10_02026-08-03redhat
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
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 rangeFixed inDependents
mariadb10.11.17-r0
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
mariadb11.4.11-r0
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
mariadb11.4.11-r0
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
mariadb11.4.11-r0
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
mariadb11.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

Weakness Classification(2)

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 16× in last 7d / 78× 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 152 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-44173?
CVE-2026-44173 is a medium vulnerability published on June 12, 2026. MariaDB server is a community developed fork of MySQL server. From versions 10.6.1 to before 10.6.26, 10.11.1 to before 10.11.17, 11.4.1 to before 11.4.11, 11.8.1 to before 11.8.7, and 12.3.1, MariaDB allowed SELECT ... INTO OUTFILE and SELECT ... INTO DUMPFILE without verifying the FILE privilege…
When was CVE-2026-44173 disclosed?
CVE-2026-44173 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44173 actively exploited?
CVE-2026-44173 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 52.9% of all scored CVEs.
What is the CVSS score of CVE-2026-44173?
CVE-2026-44173 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-44173?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44173, 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-44173

Explore →

Is Your Infrastructure Affected by CVE-2026-44173?

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