CVE-2026-44171

HIGHNVD 7.87.8—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.8 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 93% 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
7.8EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 7.8Exploit: None knownExposed services: Not assessed

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, mbstream did not check for /../ in the path when unpacking the archive. A proper backup can never contain such paths, but a specially crafted archive could have caused mbstream to create files outside of the target-dir path. 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
7.8
EG Score
7.8HIGHmedium confidence
EG Risk
40
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
EPSS PROB
0.2%
EPSS %ILE
6th
KEV
Not listed

Published

June 12, 2026

Last Modified

June 16, 2026

Advisory Details (2)

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

[MDEV-39408] mbstream insufficient path validation - Jira

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

path traversal in mbstream · 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-9pjh-5hhw-65v9

Vendor Advisories for CVE-2026-44171(8)

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

Patch Availability(9)

Vendor / EcosystemFix (by version range) / PatchReleasedSource
ubuntumariadb-test-data (1:11.8.6-5ubuntu0.1) @ resolute2026-09-14ubuntu
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 rangeFix by version rangeDependents
mariadb—
  • 10.6.1 up to 10.11.17-r0: fixed in 10.11.17-r0
—
Alpine:v3.21(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 10.6.1 up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.22(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 10.6.1 up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.23(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 10.6.1 up to 11.4.11-r0: fixed in 11.4.11-r0
—
Alpine:v3.24(1)
PackageVulnerable rangeFix by version rangeDependents
mariadb—
  • 10.6.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:10.11.9-0+deb12u1 (21 versions)
  • every version up to 1:10.11.18-0+deb12u1: fixed in 1:10.11.18-0+deb12u1
—
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

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

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

Frequently asked(5)

What is CVE-2026-44171?
CVE-2026-44171 is a high 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, mbstream did not check for /../ in the path when unpacking the archive. A proper backup can never contain…
When was CVE-2026-44171 disclosed?
CVE-2026-44171 was first published on June 12, 2026, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44171 actively exploited?
CVE-2026-44171 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (6th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2026-44171?
CVE-2026-44171 has a CVSS v3 base score of 7.8 (NVD).
How do I remediate CVE-2026-44171?
A fix for CVE-2026-44171 is available: update to the fixed version the vendor names in its advisory. The vendor advisories EchelonGraph has for CVE-2026-44171 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-44171

Explore →

Is Your Infrastructure Affected by CVE-2026-44171?

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

Book a Demo →Browse All CVEs