Skip to main content

Bitnami MariaDB Galera CVE-2026-47847

| EUVDEUVD-2026-37931 MEDIUM
Use of Hard-coded Credentials (CWE-798)
2026-06-18 vmware
5.3
CVSS 3.1 · Vendor: vmware
Share

Severity by source

Vendor (vmware) PRIMARY
5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
vuln.today AI
5.3 MEDIUM

Publicly known credentials negate the authentication barrier (PR:N, AC:L); REPLICATION CLIENT access yields read-only replication metadata, not table data (C:L, I:N, A:N).

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (vmware).

CVSS VectorVendor: vmware

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

2
Patch available
Jun 18, 2026 - 21:02 EUVD
Analysis Generated
Jun 18, 2026 - 20:01 vuln.today

DescriptionCVE.org

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.

AnalysisAI

Hardcoded default credentials in Bitnami MariaDB Galera container images and Helm chart expose all default deployments to unauthenticated replication status enumeration over the network. The health-check user monitor with password monitor is granted REPLICATION CLIENT privileges from any host (%), meaning any network-accessible cluster running affected images (10.6.x through 12.3.x) or Helm chart prior to 18.3.0 can be accessed using these publicly known credentials. …

Unlock full vulnerability intelligence

  • Risk assessment & exploitation conditions
  • Attack chain visualization
  • Remediation with exact patch versions
  • Threat intelligence from 22 sources
  • Personal watchlist & email alerts

Free forever · No credit card required

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata

Access
Identify network-accessible MariaDB Galera port
Delivery
Connect using publicly known 'monitor'/'monitor' credentials
Exploit
Authenticate as REPLICATION CLIENT user
Execution
Execute SHOW MASTER/SLAVE STATUS commands
Impact
Enumerate cluster topology, primary node identity, and binary log state

Vulnerability AssessmentAI

Exploitation Exploitation requires network reachability to the MariaDB service port (default 3306) on a deployment running an affected Bitnami MariaDB Galera container image or Helm chart. … Additional conditions and limiting factors are described in the full assessment.
Risk Assessment The NVD-assigned CVSS 3.1 score of 5.3 (Medium) with vector AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N correctly captures the low-complexity, network-accessible nature of the flaw and accurately limits impact to low confidentiality (REPLICATION CLIENT yields replication metadata, not table data). … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in.
Exploit Scenario An attacker with network access to a Kubernetes cluster running an unpatched Bitnami MariaDB Galera deployment connects to port 3306 on any cluster node using the publicly documented credentials `monitor`/`monitor`, requiring only a standard MySQL client. Once authenticated as the replication user, they execute `SHOW SLAVE STATUS`, `SHOW MASTER STATUS`, and `SHOW BINARY LOGS` to map the cluster's replication topology, identify the primary write node, and determine binary log positions - information useful for planning targeted follow-on attacks such as targeted disruption of the primary or timing-based data extraction attempts. …
Remediation The primary fix is to upgrade to patched container image tags - 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 - and to upgrade the Helm chart to version 18.3.0 or later, which introduces configurable Helm values for the replication user credentials. … Detailed patch versions, workarounds, and compensating controls in full report.

Threat intelligence, references, and detailed analysis are available after sign-in.

Share

CVE-2026-47847 vulnerability details – vuln.today

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy