Categories
CVE-2026-47847 medium CVSS 5.3

Vulnerability in mariadb-galera (CVE-2026-47847)

Summary

Vulnerability in mariadb-galera (CVE-2026-47847). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.6.27-0, 10.11.17-0, 11.4.12-0, 11.8.7-0, 12.3.2-0 or later.

Original description

The description as published by the source.

Bitnami MariaDB Galera container images and Helm chart are affected by a hardcoded default credential vulnerability in the Galera replication health-check user. The MARIADB_REPLICATION_USER and MARIADB_REPLICATION_PASSWORD environment variables defaulted to monitor and monitor respectively. This user is granted REPLICATION CLIENT privileges from any host ('%'). The Bitnami Helm chart for MariaDB Galera did not expose parameters to configure this user's credentials, resulting in all chart deployments using this publicly known credential by default. A remote attacker with network access to the MariaDB port can authenticate as monitor:monitor and query replication topology and status information.

Source: NIST National Vulnerability Database NVD

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-47847 has been found in mariadb-galera.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade mariadb-galera to 10.6.27-0, 10.11.17-0, 11.4.12-0, 11.8.7-0, 12.3.2-0 or later.
If unsure, ask your IT team or search "mariadb-galera CVE-2026-47847" on the vendor's site.

CVE-2026-47847 (mariadb-galera) — CWE-798 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 10.6.27-0, 10.11.17-0, 11.4.12-0, 11.8.7-0, 12.3.2-0 — 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.

❓ What is the problem

A vulnerability (CWE-798) exists in mariadb-galera.

📍 Affected scope

Check the vendor advisory for the affected versions of mariadb-galera.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 10.6.27-0, 10.11.17-0, 11.4.12-0, 11.8.7-0, 12.3.2-0.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mariadb-galera' . 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

  1. 1
    Identify exposure identify
    grep -r 'mariadb-galera' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mariadb-galera を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade mariadb-galera to 10.6.27-0, 10.11.17-0, 11.4.12-0, 11.8.7-0, 12.3.2-0

    ステージング環境で 10.6.27-0, 10.11.17-0, 11.4.12-0, 11.8.7-0, 12.3.2-0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Bitnami mariadb-galera
[{"type":"SEMVER","events":[{"introduced":"10.6.0"},{"fixed":"10.6.27-0"},{"introduced":"10.11.0"},{"fixed":"10.11.17-0"},{"introduced":"11.4.0"},{"fixed":"11.4.12-0"},{"introduced":"11.8.0"},{"fixed":"11.8.7-0"},{"introduced":"12.3.0"},{"fixed":"12.3.2-0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details