ZDF
Sign inSign up

Vulnerabilities

Vulnerability · CVE-2025-2506

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

Published May 22, 2025 · catalog updated Aug 26, 2025 · EnterpriseDB BDR/PGD

Check if you run it

No confirmed exploitation is on record for CVE-2025-2506. EPSS is 0.31%. Act only if a listed version of EnterpriseDB BDR/PGD is installed.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
Medium5.3
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
0.31%
Remediation
Version ranges on file
Affected products
vendor EnterpriseDB BDR/PGD 4 <4.3.8-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 permission

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor EnterpriseDB BDR/PGD 4 <4.3.8-ELS4 <4.3.8-ELS

How to fix CVE-2025-2506

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

No confirmed exploitation is on record for CVE-2025-2506. EPSS is 0.31%. Act only if a listed version of EnterpriseDB BDR/PGD is installed.

Which versions are affected?

Compare what you have installed with EnterpriseDB BDR/PGD 4 <4.3.8-ELS 4 <4.3.8-ELS. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 0.31%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. May 22, 2025 · EUVD

    Detected

    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 introdu

  2. Aug 26, 2025 · EUVD

    Updated

    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 introdu

Sources

  • CVE.orgVulnerability recordCVE-2025-2506

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2025-2506

    30-day exploitation probability 0.3%

    first.org
  • EUVDVulnerability recordEUVD-2025-27726

    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

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Oct 18, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.