https://db.gcve.eu Contains only the most 10 recent sightings. http://www.rssboard.org/rss-specification python-feedgen en Tue, 30 Jun 2026 14:42:52 +0000 https://db.gcve.eu/sighting/28af6e90-59fb-4359-a245-f286622a0f2a/export {"uuid": "28af6e90-59fb-4359-a245-f286622a0f2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-mx38-x658-5fwj", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114500499510580526", "content": "", "creation_timestamp": "2025-05-13T12:22:50.101217Z"} {"uuid": "28af6e90-59fb-4359-a245-f286622a0f2a", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-mx38-x658-5fwj", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114500499510580526", "content": "", "creation_timestamp": "2025-05-13T12:22:50.101217Z"} https://db.gcve.eu/sighting/28af6e90-59fb-4359-a245-f286622a0f2a/export Tue, 13 May 2025 12:22:50 +0000 https://db.gcve.eu/sighting/40596b93-4486-417c-8961-2d88b8478a69/export {"uuid": "40596b93-4486-417c-8961-2d88b8478a69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-mx38-x658-5fwj", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114500496210973102", "content": "", "creation_timestamp": "2025-05-13T12:22:00.117041Z"} {"uuid": "40596b93-4486-417c-8961-2d88b8478a69", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-mx38-x658-5fwj", "type": "seen", "source": "https://infosec.exchange/users/cR0w/statuses/114500496210973102", "content": "", "creation_timestamp": "2025-05-13T12:22:00.117041Z"} https://db.gcve.eu/sighting/40596b93-4486-417c-8961-2d88b8478a69/export Tue, 13 May 2025 12:22:00 +0000 https://db.gcve.eu/sighting/25667f38-ec1d-4db5-a528-26f84fa1b1fb/export {"uuid": "25667f38-ec1d-4db5-a528-26f84fa1b1fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-MX38-X658-5FWJ", "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": "25667f38-ec1d-4db5-a528-26f84fa1b1fb", "vulnerability_lookup_origin": "1a89b78e-f703-45f3-bb86-59eb712668bd", "author": "2a075640-a300-48a4-bb44-bc6130783b9b", "vulnerability": "GHSA-MX38-X658-5FWJ", "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"} https://db.gcve.eu/sighting/25667f38-ec1d-4db5-a528-26f84fa1b1fb/export Tue, 13 May 2025 09:30:38 +0000