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 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.

Published: 2025-05-22 Last update: 2026-04-15 Assigner: 20be33e2-bf35-4d13-8fad-18bd2f3e3659 Source: 20be33e2-bf35-4d13-8fad-18bd2f3e3659
NVD Status：Deferred，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2025-2506 is rated Low Risk (36/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.20%). Monitor for updates and reassess as exploit intelligence or EPSS changes.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2025-2506

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-03-18 0.06% 0.20% +0.14%
2 2026-02-05 0.02% 0.06% +0.04%
3 2025-05-23 — 0.02% —

Full EPSS history (3 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2025-2506

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
5.3 3.1 MEDIUM
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
 1.6 3.6 20be33e2-bf35-4d13-8fad-18bd2f3e3659

Weakness enumeration for CVE-2025-2506

OS Trackers for CVE-2025-2506

vendor priority summary link
debian unimportant CVE-2025-2506 unimportant priority: Debian including 1 source packages (pglogical), 5 status rows across 5 suites (bookworm, bullseye, forky, sid, trixie): resolved 5. https://security-tracker.debian.org/tracker/CVE-2025-2506
ubuntu medium CVE-2025-2506 medium priority: Ubuntu including 1 source packages (pglogical), 7 status rows across 7 suites (bionic, focal, jammy, noble, oracular, plucky, upstream): not-affected 6, needs-triage 1. https://ubuntu.com/security/CVE-2025-2506

Affected software / configurations for CVE-2025-2506

Vendor Product Version Raw CPE
No affected products in dataset.

References for CVE-2025-2506

cvelogic Threat Intelligence