CVE-2026-44170

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 0.8%, top 47% 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
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 1%CVSS: 9.8Exploit: NoneExposed: 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 on WIndows with installed CONNECT engine and enabled REST support interpolated table HTTP attribute into the curl command line without proper sanitizing. This allows the user to execute shell commands on the server. 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
9.8
EG Score
9.8(medium)
EG Risk
44(Track)
EG Risk 44/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
Severity98% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
52.7%
KEV
Not listed

Published

June 12, 2026

Last Modified

July 15, 2026

Advisory Details (12)

Auto-updated Jul 16, 2026
Patch available. Sources: github, redhat.
redhat Patch Available

cve-details

https://access.redhat.com/security/cve/CVE-2026-44170
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:33482
redhat Patch Available

Affected: Red Hat Enterprise Linux 9.

https://access.redhat.com/errata/RHSA-2026:33481
redhat Patch Available

Affected: Red Hat Enterprise Linux 8.

https://access.redhat.com/errata/RHSA-2026:33464
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:33412
redhat Patch Available

Affected: Red Hat Enterprise Linux 10.

https://access.redhat.com/errata/RHSA-2026:33093
generic

[MDEV-39289] CONNECT REST support on Windows doesn't escape the url - Jira

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

Argument injection in CONNECT REST Xcurl on Windows via unsanitized URL · 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-f835-cfjq-wf73
redhat Patch Available

Affected: Red Hat Enterprise Linux 10",

https://security.access.redhat.com/data/csaf/v2/vex/2026/cve-2026-44170.json
redhat

2488451 – (CVE-2026-44170) CVE-2026-44170 mariadb: Arbitrary shell command execution via improper sanitization in CONNECT engine

https://bugzilla.redhat.com/show_bug.cgi?id=2488451

Patch Availability(7)

Vendor / EcosystemFixed in / PatchReleasedSource
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
redhatmariadb:11.8-9080020260612104015.rhel92026-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(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

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

Frequently asked(5)

What is CVE-2026-44170?
CVE-2026-44170 is a critical 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 on WIndows with installed CONNECT engine and enabled REST support interpolated table HTTP…
When was CVE-2026-44170 disclosed?
CVE-2026-44170 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-44170 actively exploited?
CVE-2026-44170 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 52.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44170?
CVE-2026-44170 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-44170?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44170, 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-44170

Explore →

Is Your Infrastructure Affected by CVE-2026-44170?

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