CVE-2026-48163

HIGHNVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under NVD CVSS v3. EPSS exploit probability: 0.9%, top 42% 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.2EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 7.2Exploit: 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.27, 10.11.1 to before 10.11.18, 11.4.1 to before 11.4.12, 11.8.1 to before 11.8.8, 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 rsync SST method. This issue has been patched in versions 10.6.27, 10.11.18, 11.4.12, 11.8.8, and 12.3.2.

CVSS v3
7.2
EG Score
7.2(medium)
EG Risk
33(Track)
EG Risk 33/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
Severity72% × 45%
Exploitation1% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
58%
KEV
Not listed

Published

June 12, 2026

Last Modified

August 3, 2026

Advisory Details (2)

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

[MDEV-39648] wsrep_sst_rsync.sh: apply safe() to joiner-supplied parameters - Jira

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

wsrep SST unsafe parameter handling on the donor side (rsync) · Advisory · MariaDB/server · GitHub

Affected: 10.6.27, 10.11.18, 11.4.12, 11.8.8, 12.3.2.

https://github.com/MariaDB/server/security/advisories/GHSA-rpgv-q6gv-684r

Vendor Advisories for CVE-2026-48163(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-09-14ubuntu
redhatmariadb10.11-3:10.11.18-1.el10_02026-08-03redhat
redhatmariadb:11.8-9080020260612104015.rhel92026-06-30redhat
redhatmariadb:10.11-9080020260612103452.rhel92026-06-30redhat
redhatmariadb:10.11-8100020260616102001.489197e62026-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.

Affected Packages

(8 across 8 ecosystems)
Alpine:v3.20(1)
PackageVulnerable rangeFixed inDependents
mariadb—10.11.18-r0—
Alpine:v3.21(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.12-r0—
Alpine:v3.22(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.12-r0—
Alpine:v3.23(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.4.12-r0—
Alpine:v3.24(1)
PackageVulnerable rangeFixed inDependents
mariadb—11.8.8-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.9+ds-1 (20 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 6× in last 7d / 39× 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 216 total refreshes for this CVE.

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

Related CVEs(same vendor + same CWE)

Frequently asked(5)

What is CVE-2026-48163?
CVE-2026-48163 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.27, 10.11.1 to before 10.11.18, 11.4.1 to before 11.4.12, 11.8.1 to before 11.8.8, 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-48163 disclosed?
CVE-2026-48163 was first published in the National Vulnerability Database on June 12, 2026, with the most recent update on August 3, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-48163 actively exploited?
CVE-2026-48163 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 41.8% of all scored CVEs.
What is the CVSS score of CVE-2026-48163?
CVE-2026-48163 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-48163?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-48163, 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-48163

Explore →

Is Your Infrastructure Affected by CVE-2026-48163?

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

Start Free Scan →Browse All CVEs