Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2025-22248: The bitnami/pgpool Docker image, and the bitnami/postgres-ha k8s chart, under default configurations, comes wi

47
This month
HIGH 7.5REMOTEWATCHLISTUPGRADEUPGRADE

CVE-2025-22248 is a high-severity flaw (CVSS 7.5) affecting bitnami, bitnami\/pgpool. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The bitnami/pgpool Docker image, and the bitnami/postgres-ha k8s chart, under default configurations, comes with an 'repmgr' user that allows unauthenticated access to the database inside the cluster. The PGPOOL_SR_CHECK_USER is the user that Pgpool itself uses to perform streaming replication checks against nodes, and should not be at trust level. This allows to log into a PostgreSQL database using the repgmr user without authentication. If Pgpo

Why this priority

  • High severity
  • Remotely exploitable, no login, no user action
  • On your watchlist

A fixed release or distro patch exists.

Risk facts

CVSS score7.5 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionNone
EPSS exploit chance0.5% (top 57%)
CISA exploited listNo
WeaknessCWE-1188
Published2025-05-13
Last modified2026-06-17
Publisher (CNA): VMware · Vendor: broadcom

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

broadcom bitnami UPGRADE
Affected: < 16.0.0
Fixed in: 16.0.0
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy bitnami || rpm -q bitnami || bitnami --version
2. UPGRADE to 16.0.0 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bitnami
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bitnami
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
broadcom bitnami\/pgpool UPGRADE
Affected: < 4.6.0-1
Fixed in: 4.6.0-1
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy bitnamipgpool || rpm -q bitnamipgpool || bitnamipgpool --version
2. UPGRADE to 4.6.0-1 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade bitnamipgpool
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade bitnamipgpool
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2025-22248?

bitnami: upgrade to 16.0.0; bitnami\/pgpool: upgrade to 4.6.0-1. Exact commands for each OS are on this page.

Is CVE-2025-22248 being exploited?

CVE-2025-22248 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2025-22248 affect?

CVE-2025-22248 affects bitnami, bitnami\/pgpool. Severity is high (CVSS 7.5). The bitnami/pgpool Docker image, and the bitnami/postgres-ha k8s chart, under default configurations, comes with an 'repmgr' user that allows unauthenticated access to the database inside the cluster. The PGPOOL_SR_CHECK_USER is the user th

How urgent is CVE-2025-22248?

Priority 47/100. High severity; Remotely exploitable, no login, no user action; On your watchlist

Software pages

Docker vulnerabilities · Kubernetes vulnerabilities · PostgreSQL vulnerabilities

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.