CVE-2026-44168

HIGHPre-NVD 8.08.0—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 8.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.6%, top 56% 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
8.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 8.0Exploit: 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, during the SST the donor node is interpolating parameters that the joiner sent into the command line. Not all parameters were properly validated which could allow a malicious joiner to execute arbitrary shell commands on the donor side via the mariabackup SST method. 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
8.0
EG Score
8.0(medium)
EG Risk
36(Track)
EG Risk 36/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
Severity80% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
44%
KEV
Not listed

Published

June 12, 2026

Last Modified

July 15, 2026

Advisory Details (2)

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

[MDEV-39413] wsrep unsafe handling of parameters - Jira

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

wsrep SST unsafe parameter handling on the donor side · 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-vwf7-w26c-9w5h

Vendor Advisories for CVE-2026-44168(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-26ubuntu
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
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

(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 22× in last 7d / 70× 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 110 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-44168?
CVE-2026-44168 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, during the SST the donor node is interpolating parameters that the joiner sent into the command line. Not…
When was CVE-2026-44168 disclosed?
CVE-2026-44168 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-44168 actively exploited?
CVE-2026-44168 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 56.2% of all scored CVEs.
What is the CVSS score of CVE-2026-44168?
CVE-2026-44168 has a CVSS v3 base score of 8.0 (NVD).
How do I remediate CVE-2026-44168?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44168, 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-44168

Explore →

Is Your Infrastructure Affected by CVE-2026-44168?

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

Start Free Scan →Browse All CVEs