CVE-2020-15180: A flaw was found in the mysql-wsrep component of mariadb

This week

CRITICAL 9.0REMOTEWATCHLISTUPGRADEMITIGATEUPGRADE

CVE-2020-15180 is a critical-severity flaw (CVSS 9.0) affecting mariadb, debian linux, xtradb cluster. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

A flaw was found in the mysql-wsrep component of mariadb. Lack of input sanitization in `wsrep_sst_method` allows for command injection that can be exploited by a remote attacker to execute arbitrary commands on galera cluster nodes. This threatens the system's confidentiality, integrity, and availability. This flaw affects mariadb versions before 10.1.47, before 10.2.34, before 10.3.25, before 10.4.15 and before 10.5.6.

Why this priority

Critical severity
EPSS top 7%: very likely to be exploited
Remotely exploitable, no login, no user action
On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score	9.0 (Critical)
Attack vector	Network (remote)
Attack complexity	High
Privileges needed	None
User interaction	None
EPSS exploit chance	5.5% (top 7%)
CISA exploited list	No
Weakness	CWE-20, CWE-77
Published	2021-05-27
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: debian · galeracluster · mariadb · percona

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2021-05-27 20:15 UTCPublished CVE record published
2026-06-17 02:56 UTCUpdated Record last modified

mariadb mariadb UPGRADE

Affected: >= 10.1.0 and < 10.1.47 · >= 10.2.0 and < 10.2.34 · >= 10.3.0 and < 10.3.25 · >= 10.4.0 and < 10.4.15 · >= 10.5.0 and < 10.5.6

Fixed in: 10.1.47, 10.2.34, 10.3.25, 10.4.15, 10.5.6

Safe to downgrade to: a release before 10.1.0

1. Check installed version

apt-cache policy mariadb || rpm -q mariadb || mariadb --version

2. UPGRADE to 10.1.47 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade mariadb

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade mariadb

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 10.1.0 (Debian / Ubuntu)

apt-cache madison mariadb sudo apt install mariadb=<VERSION_BEFORE_10.1.0> sudo apt-mark hold mariadb

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list mariadb sudo dnf downgrade mariadb-<VERSION_BEFORE_10.1.0> sudo dnf versionlock add mariadb

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

debian debian linux MITIGATE

Affected: 9.0 · 10.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 9.0

Check your OS release

cat /etc/os-release; uname -r

Debian / Ubuntu

sudo apt update && sudo apt full-upgrade

RHEL / Amazon Linux / Fedora

sudo dnf upgrade --refresh

Windows

Install the latest cumulative update from Windows Update

If no patch exists yet

OS downgrades are not safe. Apply the vendor mitigation from the advisory and restrict exposure.

percona xtradb cluster UPGRADE

Affected: < 5.6.49-28.42.2 · >= 5.7 and < 5.7.31-31.45.2 · >= 8.0 and < 8.0.20-11.2

Fixed in: 5.6.49-28.42.2, 5.7.31-31.45.2, 8.0.20-11.2

Safe to downgrade to: a release before 5.7

1. Check installed version

apt-cache policy xtradb-cluster || rpm -q xtradb-cluster || xtradb-cluster --version

2. UPGRADE to 5.6.49-28.42.2 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade xtradb-cluster

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade xtradb-cluster

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 5.7 (Debian / Ubuntu)

apt-cache madison xtradb-cluster sudo apt install xtradb-cluster=<VERSION_BEFORE_5.7> sudo apt-mark hold xtradb-cluster

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list xtradb-cluster sudo dnf downgrade xtradb-cluster-<VERSION_BEFORE_5.7> sudo dnf versionlock add xtradb-cluster

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

galeracluster galera cluster for mysql UPGRADE

Affected: >= 5.6 and < 5.6.49 · >= 5.7 and < 5.7.31 · >= 8.0 and < 8.0.21

Fixed in: 5.6.49, 5.7.31, 8.0.21

Safe to downgrade to: a release before 5.6

1. Check installed version

apt-cache policy galera-cluster-for-mysql || rpm -q galera-cluster-for-mysql || galera-cluster-for-mysql --version

2. UPGRADE to 5.6.49 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade galera-cluster-for-mysql

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade galera-cluster-for-mysql

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

3. If no update is available yet, DOWNGRADE to a release before 5.6 (Debian / Ubuntu)

apt-cache madison galera-cluster-for-mysql sudo apt install galera-cluster-for-mysql=<VERSION_BEFORE_5.6> sudo apt-mark hold galera-cluster-for-mysql

3. If no update is available yet, DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list galera-cluster-for-mysql sudo dnf downgrade galera-cluster-for-mysql-<VERSION_BEFORE_5.6> sudo dnf versionlock add galera-cluster-for-mysql

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2020-15180?

mariadb: upgrade to 10.1.47, 10.2.34, 10.3.25, 10.4.15, 10.5.6; debian linux: mitigate or apply the listed mitigation; xtradb cluster: upgrade to 5.6.49-28.42.2, 5.7.31-31.45.2, 8.0.20-11.2. Exact commands for each OS are on this page.

Is CVE-2020-15180 being exploited?

CVE-2020-15180 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2020-15180 affect?

CVE-2020-15180 affects mariadb, debian linux, xtradb cluster. Severity is critical (CVSS 9.0). A flaw was found in the mysql-wsrep component of mariadb. Lack of input sanitization in `wsrep_sst_method` allows for command injection that can be exploited by a remote attacker to execute arbitrary commands on galera cluster nodes. This t

How urgent is CVE-2020-15180?

Priority 65/100. Critical severity; EPSS top 7%: very likely to be exploited; Remotely exploitable, no login, no user action; On your watchlist

Software pages

MySQL vulnerabilities · MariaDB vulnerabilities · Debian vulnerabilities

Related CVEs

CVE-2026-97380 HIGH 8.8 UPGRADE MariaDB server is a community developed fork of MySQL server
CVE-2026-49261 CRITICAL 10.0 UPGRADE MariaDB server is a community developed fork of MySQL server
CVE-2026-44170 CRITICAL 9.8 UPGRADE MariaDB server is a community developed fork of MySQL server
CVE-2026-44172 CRITICAL 9.1 DOWNGRADE MITIGATE MariaDB server is a community developed fork of MySQL server
CVE-2026-48165 HIGH 8.0 UPGRADE MariaDB server is a community developed fork of MySQL server

References

← Back to latest CVEs