dbcve.org
Hard-coded CredentialsWeakness · CWE-798

CVE-2026-47847

MEDIUM · 5.3 CVSS v3.1 Published 2026-06-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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. Affected versions — Container image: 10.6.x prior to 10.6.27-photon-5-r0; 10.11.x prior to 10.11.17-photon-5-r1; 11.4.x prior to 11.4.12-photon-5-r0; 11.8.x prior to 11.8.7-photon-5-r1; 12.3.x prior to 12.3.2-photon-5-r0 / 12.3.2-debian-12-r0. Helm chart: prior to 18.3.0.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Bitnami MariaDB Galera container images and Helm chart contain hardcoded default credentials (username: monitor, password: monitor) for a Galera replication health-check user granted REPLICATION CLIENT privileges from any host. The Helm chart lacked parameters to configure custom credentials, causing all default deployments to use publicly known credentials.

MitigationUpgrade to patched container image versions (10.6.27+, 10.11.17+, 11.4.12+, 11.8.7+, 12.3.2+) and Helm chart version 18.3.0+, then change the default MARIADB_REPLICATION_USER and MARIADB_REPLICATION_PASSWORD to strong, unique values.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Bitnami MariaDB Galera is deployed
    Check container image tags or Helm release for Bitnami MariaDB or MariaDB Galera components (e.g., run 'kubectl get deployments' or 'helm list' and inspect image names)
    Affected if Deployment uses Bitnami MariaDB Galera container images or Helm chart
  2. Check for hardcoded replication user
    Inspect environment variables MARIADB_REPLICATION_USER or similar in the deployment config, pod spec, or Helm values.yaml
    Affected if MARIADB_REPLICATION_USER is set to the default value 'monitor' or is not customized
  3. Check for hardcoded replication password
    Inspect environment variable MARIADB_REPLICATION_PASSWORD or similar in the deployment config, pod spec, or Helm values.yaml
    Affected if MARIADB_REPLICATION_PASSWORD is set to the default value 'monitor' or is not customized (empty/default)
  4. Verify replication user privileges in database
    Connect to MariaDB and run: SELECT user, host, privileges FROM mysql.user WHERE user='monitor'; or check if a replication health-check user exists with REPLICATION CLIENT privileges from '%'
    Affected if A 'monitor' user exists with REPLICATION CLIENT privileges granted from any host ('%')
  5. Check Helm chart version
    Run 'helm list' and inspect the chart version for the MariaDB Galera release, or check values.yaml for the chart version
    Affected if Helm chart version is below 18.3.0 (or image tags are below 10.6.27, 10.11.17, 11.4.12, 11.8.7, or 12.3.2)

A user is affected if their Bitnami MariaDB Galera deployment uses default 'monitor'/'monitor' credentials for the replication user, or if the Helm chart version is below 18.3.0 with uncustomized replication credentials.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to patched container image versions (10.6.27+, 10.11.17+, 11.4.12+, 11.8.7+, 12.3.2+) and Helm chart version 18.3.0+, then change the default MARIADB_REPLICATION_USER and MARIADB_REPLICATION_PASSWORD to strong, unique values.

Recommended fix High confidence

Container image: 10.6.27-photon-5-r0 / 10.11.17-photon-5-r1 / 11.4.12-photon-5-r0 / 11.8.7-photon-5-r1 / 12.3.2-photon-5-r0 or 12.3.2-debian-12-r0; Helm chart: 18.3.0

  1. 1. For container image deployments: Upgrade the MariaDB Galera container image to version 10.6.27-photon-5-r0 or later for the 10.6.x branch, 10.11.17-photon-5-r1 or later for the 10.11.x branch, 11.4.12-photon-5-r0 or later for the 11.4.x branch, 11.8.7-photon-5-r1 or later for the 11.8.x branch, or 12.3.2-photon-5-r0/12.3.2-debian-12-r0 or later for the 12.3.x branch
  2. 2. For Helm chart deployments: Upgrade the Bitnami MariaDB Galera Helm chart to version 18.3.0 or later
  3. 3. After upgrading, verify that the MARIADB_REPLICATION_USER and MARIADB_REPLICATION_PASSWORD environment variables are configured with unique, strong credentials rather than the default 'monitor'/'monitor' values
  4. 4. If deploying new instances, ensure custom credentials are provided via environment variables or chart values
  5. 5. For existing deployments, rotate the replication user credentials to non-default values
Caveat Upgrade is minor/patch within same major version branches; minimal risk expected but test in non-production first

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47847 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-47847 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data