CVE-2025-2506
Description
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.
How to fix
- EnterpriseDB pglogical3.7.26-ELS or later
- EnterpriseDB BDR/PGD4.3.8-ELS, 5.8.0 or later
Affected products
| Product | Affected versions | Fixed in |
|---|---|---|
| EnterpriseDB pglogical | 3 ≤ v < 3.7.26-ELS | 3.7.26-ELS |
| EnterpriseDB BDR/PGD | 4 ≤ v < 4.3.8-ELS, 5 ≤ v < 5.8.0 | 4.3.8-ELS, 5.8.0 |
Check your version
Choose the product and enter the version you run to see whether it falls in the affected range.
Attack Surface Management
See the assets tied to your domains, the technologies they run and known vulnerabilities in one list.