CVE-2025-2506

published 22 May 2025 · updated 26 Aug 2025

When pglogical attempts to replicate data, it does not verify it is using a replication connection, which means a user with CONNECT access…

5.3MediumCVSS 5.3EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 4.3.8-ELS, 5.8.0 and 3.7.26-ELS.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
EnterpriseDB>=4 <4.3.8-ELS, >=5 <5.8.0, >=3 <3.7.26-ELS4.3.8-ELS, 5.8.0, 3.7.26-ELS

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2025-2506 severity on Zeptric[![CVE-2025-2506](https://zeptric.io/badge/cve/CVE-2025-2506.svg)](https://zeptric.io/cve/CVE-2025-2506)