CVE-2026-48163: MariaDB: wsrep SST unsafe parameter handling on the donor side (rsync)

Published Jun 12, 2026
·
Updated

Last updated 11 July 2026

Other sources

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.

— Red Hat

Affected Software

7 affected componentsFixes available
MariaDB MariaDB Server>=10.6.1<10.6.27, >=10.11.1<10.11.18, >=11.4.1<11.4.12, >=11.8.1<11.8.8, =12.3.1
MariaDB MariaDB>=10.6.1<10.6.27
MariaDB MariaDB>=10.11.1<10.11.18
MariaDB MariaDB>=11.4.1<11.4.12
MariaDB MariaDB>=11.8.1<11.8.8
MariaDB MariaDB=12.3.1
debian/mariadb<=1:11.8.6-0+deb13u1
1:10.11.18-0+deb12u11:11.8.8-1

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade debian/mariadb to a version that resolves this vulnerability.

    Fixed in 1:10.11.18-0+deb12u1Fixed in 1:11.8.8-1
  2. Upgrade

    Upgrade MariaDB server (wsrep SST via rsync) to a version that resolves this vulnerability.

    Fixed in 10.6.27
  3. Upgrade

    Upgrade MariaDB server (wsrep SST via rsync) to a version that resolves this vulnerability.

    Fixed in 10.11.18
  4. Upgrade

    Upgrade MariaDB server (wsrep SST via rsync) to a version that resolves this vulnerability.

    Fixed in 11.4.12
  5. Upgrade

    Upgrade MariaDB server (wsrep SST via rsync) to a version that resolves this vulnerability.

    Fixed in 11.8.8
  6. Upgrade

    Upgrade MariaDB server (wsrep SST via rsync) to a version that resolves this vulnerability.

    Fixed in 12.3.2

Event History

Jun 12, 2026
CVE Published
via MITRE·05:34 PM
Data Sourced
via MITRE·05:34 PM
DescriptionSeverityWeakness
Data Sourced
via Red Hat·06:01 PM
DescriptionSeverityAffected Software
Data Sourced
via NVD·06:16 PM
DescriptionSeverityWeaknessAffected Software
Jul 15, 2026
Data Sourced
via Ubuntu·01:29 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·01:34 PM
DescriptionAffected Software
Data Sourced
via Launchpad·01:34 PM
Description
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-48163?

CVE-2026-48163 has a severity rating of high (8).

2

How do I fix CVE-2026-48163?

To resolve CVE-2026-48163, upgrade to MariaDB versions 10.6.27, 10.11.18, 11.4.12, 11.8.8, or 12.3.1 or later.

3

What is the risk associated with CVE-2026-48163?

CVE-2026-48163 has a risk score of 65, indicating a significant potential impact.

4

What kind of vulnerability is CVE-2026-48163?

CVE-2026-48163 is categorized as an OS Command Injection vulnerability.

5

Which versions of MariaDB are affected by CVE-2026-48163?

CVE-2026-48163 affects MariaDB versions from 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.

Company

Resources

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203