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 57% 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
43%
KEV
Not listed

Published

June 12, 2026

Last Modified

July 15, 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

Vendor Advisories for CVE-2026-44173(7)

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:11.8-9080020260612104015.rhel92026-06-30redhat
redhatmariadb:10.11-8100020260616102001.489197e62026-06-30redhat
redhatmariadb:10.11-9080020260612103452.rhel92026-06-30redhat
redhatmariadb11.8-3:11.8.8-1.el10_22026-06-30redhat
redhatmariadb10.11-3:10.11.18-1.el10_22026-06-29redhat
redhatmariadb11-8-main-11.8.8-1.hum12026-06-10redhat
redhatmariadb10-11-main-10.11.18-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(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 11× in last 7d / 59× 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-27 14:13 UTCEPSS rescore
  2. 2026-07-26 20:36 UTCEG score recompute
  3. 2026-07-26 20:36 UTCVendor advisory
  4. 2026-07-26 14:54 UTCEPSS rescore
  5. 2026-07-26 14:54 UTCEPSS rescore
  6. 2026-07-25 14:18 UTCEPSS rescore
  7. 2026-07-24 14:17 UTCEPSS rescore
  8. 2026-07-23 03:14 UTCEG score recompute
  9. 2026-07-22 14:08 UTCEPSS rescore
  10. 2026-07-21 15:24 UTCEPSS rescore
  11. 2026-07-20 17:08 UTCEPSS rescore
  12. 2026-07-19 14:31 UTCEPSS rescore
  13. 2026-07-19 02:29 UTCEPSS rescore
  14. 2026-07-18 10:04 UTCEPSS rescore
  15. 2026-07-16 23:16 UTCVendor advisory
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-15 16:57 UTCEPSS rescore
  18. 2026-07-15 16:19 UTCEG score recompute▲ 0.30
  19. 2026-07-15 16:19 UTCVendor advisory
  20. 2026-07-15 02:26 UTCNVD updateCVSS v3 → 5.3
  21. 2026-07-15 02:00 UTCEPSS rescore
  22. 2026-07-14 13:49 UTCVendor advisory
  23. 2026-07-13 22:30 UTCEPSS rescore
  24. 2026-07-13 15:49 UTCEG score recompute▼ 0.30
  25. 2026-07-13 15:49 UTCVendor advisory
Show 58 more
  1. 2026-07-13 12:52 UTCMITRE cvelistV5CVSS v3 → 5
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-12 17:43 UTCVendor advisory
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-07-11 17:38 UTCVendor advisory
  6. 2026-07-11 08:27 UTCEPSS rescore
  7. 2026-07-10 19:39 UTCVendor advisory
  8. 2026-07-10 12:27 UTCNVD updateCVSS v3 → 5.3
  9. 2026-07-10 12:12 UTCMITRE cvelistV5CVSS v3 → 5
  10. 2026-07-09 21:41 UTCVendor advisory
  11. 2026-07-09 19:10 UTCEPSS rescore
  12. 2026-07-08 21:01 UTCVendor advisory
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-07 23:04 UTCVendor advisory
  15. 2026-07-07 13:46 UTCEPSS rescore
  16. 2026-07-07 01:05 UTCVendor advisory
  17. 2026-07-06 16:27 UTCEPSS rescore
  18. 2026-07-06 02:23 UTCEPSS rescore
  19. 2026-07-05 20:11 UTCVendor advisory
  20. 2026-07-05 02:30 UTCEPSS rescore
  21. 2026-07-04 22:13 UTCVendor advisory
  22. 2026-07-04 06:31 UTCEPSS rescore
  23. 2026-07-04 00:15 UTCVendor advisory
  24. 2026-07-03 02:17 UTCVendor advisory
  25. 2026-07-02 04:20 UTCVendor advisory
  26. 2026-07-01 15:07 UTCEPSS rescore
  27. 2026-07-01 06:23 UTCVendor advisory
  28. 2026-06-30 23:22 UTCEPSS rescore
  29. 2026-06-30 08:26 UTCVendor advisory
  30. 2026-06-29 14:06 UTCEPSS rescore
  31. 2026-06-29 10:28 UTCVendor advisory
  32. 2026-06-28 14:07 UTCEPSS rescore
  33. 2026-06-28 12:30 UTCVendor advisory
  34. 2026-06-28 04:56 UTCEPSS rescore
  35. 2026-06-27 14:34 UTCVendor advisory
  36. 2026-06-27 03:08 UTCEPSS rescore
  37. 2026-06-26 16:36 UTCVendor advisory
  38. 2026-06-25 13:49 UTCEPSS rescore
  39. 2026-06-25 13:49 UTCEPSS rescore
  40. 2026-06-24 14:05 UTCEPSS rescore
  41. 2026-06-23 21:33 UTCEPSS rescore
  42. 2026-06-22 14:25 UTCEPSS rescore
  43. 2026-06-22 14:25 UTCEPSS rescore
  44. 2026-06-21 14:56 UTCEPSS rescore
  45. 2026-06-21 14:56 UTCEPSS rescore
  46. 2026-06-21 01:59 UTCEPSS rescore
  47. 2026-06-19 19:25 UTCEPSS rescore
  48. 2026-06-18 17:52 UTCEPSS rescore
  49. 2026-06-18 17:52 UTCEPSS rescore
  50. 2026-06-17 17:53 UTCEPSS rescore
  51. 2026-06-17 10:07 UTCEG score recompute▲ 0.30
  52. 2026-06-16 19:06 UTCNVD updateCVSS v3 → 5.3
  53. 2026-06-16 17:52 UTCEPSS rescore
  54. 2026-06-15 17:49 UTCEPSS rescore
  55. 2026-06-13 23:00 UTCEPSS rescore
  56. 2026-06-12 23:12 UTCEPSS rescore
  57. 2026-06-12 20:14 UTCEG score recompute
  58. 2026-06-12 20:13 UTCNVD updatefirst tracked

Related CVEs(same vendor + same CWE)

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 July 15, 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 57.1% 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

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

Start Free Scan →Browse All CVEs