OS Command Injection in mariadb (CVE-2026-49261)
Summary
OS command injection in mariadb (CVE-2026-49261). Successful exploitation can lead to full system takeover. Exploitable via wsrep_notify_cmd. Mitigation: upgrade to 10.6.27 or later.
Original description
The description as published by the source.
MariaDB server is a community developed fork of MySQL server. Versions 10.6.1 through 10.6.26, 10.11.1 through 10.11.17, 11.4.1 through 11.4.11, 11.8.1 through 11.8.7, and 12.3.1 with wsrep_notify_cmd enabled would execute shell commands embedded in the name of the joiner node. This is fixed in 10.6.27, 10.11.18, 11.4.12, 11.8.8, and 12.3.2. As a workaround, anyone who cannot upgrade now should disable wsrep_notify_cmd.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-49261 has been found in mariadb.
Attackers can target a specific entry point like wsrep_notify_cmd over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade mariadb to 10.6.27 or later.
If unsure, ask your IT team or search "mariadb CVE-2026-49261" on the vendor's site.
CVE-2026-49261 (mariadb) — CWE-78 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: wsrep_notify_cmd
Patched: 10.6.27 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
OS command injection (CWE-78) exists in mariadb. Attackers reach the vulnerable code path via wsrep_notify_cmd without authentication.
Check the vendor advisory for the affected versions of mariadb. Attack surface: wsrep_notify_cmd.
Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.
Update to 10.6.27.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mariadb' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'mariadb' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
mariadbを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade mariadb to 10.6.27ステージング環境で 10.6.27 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
Fix status by distribution
Fixed packages published by each distribution for this CVE
- BellSoft Alpaquita BELL-CVE-2026-49261 mariadb Fixed in: 10.6.27-r0
- Debian DEBIAN-CVE-2026-49261 mariadb Fixed in: 1:10.11.18-0+deb12u1
- Ubuntu UBUNTU-CVE-2026-49261 mariadb-10.0
References
- advisory github.com
- advisory nvd.nist.gov
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory access.redhat.com
- advisory github.com
- report bugzilla.redhat.com
- web jira.mariadb.org
- web security.access.redhat.com