MariaDB: unsafe usage of `wsrep_sst_receive_address` values on the joiner side

Affected versions

NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.

• mariadb mariadb10.6.1 and later · before 10.6.27
• mariadb mariadb10.11.1 and later · before 10.11.18
• mariadb mariadb11.4.1 and later · before 11.4.12
• mariadb mariadb11.8.1 and later · before 11.8.8
• mariadb mariadb12.3.1

Versions reported by the vendor

Affected version ranges reported by the assigning authority (GitHub_M). Independent of NVD's CPE analysis and usually ahead of it.

• 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, < 12.3.2affected

Package-level exposure

OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.

Other highest-scoring records for the same primary product.

• CVE-2026-49261MariaDB server has unsafe parameter handling in `wsrep_notify_cmd`
  40Plan
• CVE-2023-26785MariaDB v10.5 was discovered to contain a remote code execution (RCE) vulnerability via UDF Code in a Shared Object File, followed by a "cre
  40Plan
• CVE-2021-27928A remote code execution issue was discovered in MariaDB 10.2 before 10.2.37, 10.3 before 10.3.28, 10.4 before 10.4.18, and 10.5 before 10.5.
  40Plan

Published before and after this one in the same product

• ← EarlierCVE-2026-44173Jun 12, 2026 · MariaDB: FILE privilege was not checked for subqueries in the FROM clause
  21Monitor
• ← EarlierCVE-2026-48163Jun 12, 2026 · MariaDB: wsrep SST unsafe parameter handling on the donor side (rsync)
  28Monitor
• Later →CVE-2026-107814Oct 9, 2026 · MariaDB: Insecure $HOME in MariaDB rpm packages
  33Monitor

FIRST EPSS daily score; only changes of 0.01 or more are recorded (step chart).

Root cause

User input is inserted as text into a shell command. The shell may interpret special characters in the input as part of the command.

A representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.

1const host = req.body.host;2exec("ping -c 1 " + host, onResult);

1const host = req.body.host;2if (!/^[a-z0-9.-]{1,253}$/i.test(host)) return res.sendStatus(400);3execFile("ping", ["-c", "1", host], onResult);

Attack context

MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.