CVE-2026-47847

MEDIUMPre-NVD 5.35.3
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 5.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
8.5%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 22, 2026

Advisory Details (1)

Auto-updated Jun 18, 2026
Patch available. Sources: github.
github Patch Available

Default replication credential monitor:monitor created · Advisory · bitnami/containers · GitHub

https://github.com/bitnami/containers/security/advisories/GHSA-xcv9-cg8m-3mf2

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 14× in last 7d / 48× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 06:13 UTCEPSS rescore
  2. 2026-07-12 18:08 UTCEG score recompute
  3. 2026-07-12 05:46 UTCEPSS rescore
  4. 2026-07-11 18:32 UTCEG score recompute
  5. 2026-07-11 08:27 UTCEPSS rescore
  6. 2026-07-10 18:56 UTCEG score recompute
  7. 2026-07-09 19:20 UTCEG score recompute
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-08 19:34 UTCEG score recompute
  10. 2026-07-08 15:16 UTCEPSS rescore
  11. 2026-07-07 19:52 UTCEG score recompute
  12. 2026-07-07 13:46 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 15:08 UTCEG score recompute
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-05 15:30 UTCEG score recompute
  17. 2026-07-05 02:30 UTCEPSS rescore
  18. 2026-07-04 15:51 UTCEG score recompute
  19. 2026-07-04 06:31 UTCEPSS rescore
  20. 2026-07-03 16:06 UTCEG score recompute
  21. 2026-07-02 16:31 UTCEG score recompute
  22. 2026-07-01 16:55 UTCEG score recompute
  23. 2026-07-01 15:07 UTCEPSS rescore
  24. 2026-06-30 23:22 UTCEPSS rescore
  25. 2026-06-30 17:19 UTCEG score recompute
Show 23 more
  1. 2026-06-29 17:31 UTCEG score recompute
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-29 14:06 UTCEPSS rescore
  4. 2026-06-28 17:55 UTCEG score recompute
  5. 2026-06-28 14:07 UTCEPSS rescore
  6. 2026-06-28 04:56 UTCEPSS rescore
  7. 2026-06-28 04:56 UTCEPSS rescore
  8. 2026-06-27 18:19 UTCEG score recompute
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-26 18:43 UTCEG score recompute
  11. 2026-06-25 19:01 UTCEG score recompute
  12. 2026-06-25 13:49 UTCEPSS rescore
  13. 2026-06-24 19:25 UTCEG score recompute
  14. 2026-06-24 14:05 UTCEPSS rescore
  15. 2026-06-23 21:33 UTCEPSS rescore
  16. 2026-06-23 21:33 UTCEPSS rescore
  17. 2026-06-23 19:24 UTCEG score recompute
  18. 2026-06-22 19:48 UTCEG score recompute
  19. 2026-06-21 20:10 UTCEG score recompute
  20. 2026-06-20 20:34 UTCEG score recompute
  21. 2026-06-19 20:58 UTCEG score recompute
  22. 2026-06-18 21:22 UTCEG score recompute
  23. 2026-06-18 21:22 UTCNVD updatefirst tracked

Frequently asked(5)

What is CVE-2026-47847?
CVE-2026-47847 is a medium vulnerability published on June 18, 2026. Bitnami MariaDB Galera container images and Helm chart are affected by a hardcoded default credential vulnerability in the Galera replication health-check user. The MARIADBREPLICATIONUSER and MARIADBREPLICATIONPASSWORD environment variables defaulted to monitor and monitor respectively. This user…
When was CVE-2026-47847 disclosed?
CVE-2026-47847 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on June 22, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-47847 actively exploited?
CVE-2026-47847 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-47847?
CVE-2026-47847 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-47847?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-47847, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-47847

Explore →

Is Your Infrastructure Affected by CVE-2026-47847?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.