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
Trending — 3 sources updated this week
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%CVSS: 7.8Exploit: 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, 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.8(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity78% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
7%
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
github Patch Available

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 / 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
mariadb—10.11.17-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.11-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.11-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.11-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.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(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 23× in last 7d / 96× 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 176 total refreshes for this CVE.

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

Related CVEs(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 in the National Vulnerability Database 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% probability of exploitation in the next 30 days, which ranks it in the top 92.8% of all 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?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44171, 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-44171

Explore →

Is Your Infrastructure Affected by CVE-2026-44171?

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

Start Free Scan →Browse All CVEs