CVE-2025-2506: EnterpriseDB pglogical vulnerability
EnterpriseDB · pglogical
Vendor fix available · Affected: EnterpriseDB pglogical · Exploitation: unlikely (under 1%)
Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.
Higher than 26% of scored CVEs
DescriptionCVE.org
When pglogical attempts to replicate data, it does not verify it is using a replication connection, which means a user with CONNECT access to a database configured for replication can execute the pglogical command to obtain read access to replicated tables. When pglogical runs it should verify it is running on a replication connection but does not perform this check. This vulnerability was introduced in the pglogical 3.x codebase, which is proprietary to EDB. The same code base has been integrated into BDR/PGD 4 and 5. To exploit the vulnerability the attacker needs at least CONNECT permissions to a database configured for replication and must understand a number of pglogical3/BDR specific commands and be able to decode the binary protocol.
Affected products3
From the CVE record. A product or version that is not listed is unknown, not unaffected.
- EnterpriseDB · pglogicalfrom 3 before 3.7.26-ELS
- EnterpriseDB · BDR/PGDfrom 4 before 4.3.8-ELS
- EnterpriseDB · BDR/PGDfrom 5 before 5.8.0
On the Atlas
Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.
- Exploitation
- Unlikely (under 1%). EPSS under 1%, or no score yet.
- CISA KEV
- Not listed
- Public check
- No public nuclei template
- Vendor
- EnterpriseDB
- Published
- May 2025
CoverageNo articles yet
No CyberSIXT article names CVE-2025-2506 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.