{"vulnerability": "cve-2025-22248", "sightings": [{"uuid": "23679f61-5bca-4430-8cd3-515e95f3d024", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22248", "type": "published-proof-of-concept", "source": "https://t.me/DarkWebInformer_CVEAlerts/16090", "content": "\ud83d\udd17 DarkWebInformer.com - Cyber Threat Intelligence\n\ud83d\udccc CVE ID: CVE-2025-22248\n\ud83d\udd25 CVSS Score: 9.4 (cvssV4_0, Vector: CVSS:4.0/AV:A/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H)\n\ud83d\udd39 Description: The bitnami/pgpool\u00a0Docker image, and the bitnami/postgres-ha\u00a0k8s chart, under default configurations, comes with an 'repmgr' user that allows unauthenticated access to the database inside the cluster.\u00a0The PGPOOL_SR_CHECK_USER\u00a0is the user that Pgpool itself uses to perform streaming replication checks against nodes, and should not be at trust\u00a0level. This allows to log into a PostgreSQL database using the repgmr\u00a0user without authentication. If Pgpool is exposed externally, a potential attacker could use this user to get access to the service. This is also present within the bitnami/postgres-ha\u00a0Kubernetes Helm chart.\n\ud83d\udccf Published: 2025-05-13T09:13:30.613Z\n\ud83d\udccf Modified: 2025-05-13T09:13:30.613Z\n\ud83d\udd17 References:\n1. https://github.com/bitnami/charts/security/advisories/GHSA-mx38-x658-5fwj", "creation_timestamp": "2025-05-13T09:30:38.000000Z"}, {"uuid": "b41551e7-dc19-45aa-96db-3e0d1c0f2c2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22248", "type": "seen", "source": "https://t.me/CyberBulletin/3264", "content": "\u26a1\ufe0fCritical Misconfiguration in Bitnami Pgpool Enables Unauthenticated PostgreSQL Access (CVE-2025-22248).\n\n#CyberBulletin", "creation_timestamp": "2025-05-14T11:38:58.000000Z"}, {"uuid": "0898bfa5-6b2f-4eb7-b503-aebbc464b053", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22248", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114500499510580526", "content": "", "creation_timestamp": "2025-05-13T12:22:50.164109Z"}, {"uuid": "a2a2ce18-a4d3-4fc4-8a1c-e285763d7045", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "cve-2025-22248", "type": "seen", "source": "https://bsky.app/profile/shiojiri.com/post/3lp4ki6p6hs24", "content": "", "creation_timestamp": "2025-05-14T08:12:32.069809Z"}, {"uuid": "2d05c894-b0b5-4bff-87d6-6c1756c1add4", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "CVE-2025-22248", "type": "seen", "source": "https://bsky.app/profile/bluesky.awakari.com/post/3lp7pggsshh2e", "content": "", "creation_timestamp": "2025-05-15T14:19:00.657494Z"}]}