CVE-2025-2506
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedWhen 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidencepglogical fails to verify it is running on a replication connection during data replication, allowing any user with CONNECT access to a replication-configured database to execute pglogical commands and gain unauthorized read access to replicated tables. The vulnerability stems from missing authorization checks in the replication code path introduced in pglogical 3.x and inherited by BDR/PGD 4 and 5.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify pglogical extension versionQuery the pg_extension catalog: SELECT extname, extversion FROM pg_extension WHERE extname IN ('pglogical', 'bdr', 'pgd');Affected if The installed version is 3.x or higher (for pglogical) or 4.x/5.x (for BDR/PGD)
-
Identify databases with pglogical replication configuredCheck for active replication nodes: SELECT node_name, database FROM pglogical.node; If this returns rows, pglogical replication is active.Affected if Any rows returned means replication is configured and the vulnerability applies
-
List users with CONNECT permission on replication-configured databasesQuery: SELECT datname, grantee FROM information_schema.database_privileges WHERE privilege_type = 'CONNECT' AND datname IN (SELECT database FROM pglogical.node);Affected if More than expected users or untrusted users have CONNECT access to replication-enabled databases
-
Check for unauthorized replication role assignmentsReview pg_roles for users granted replication-related roles (pglogical.replication_writer, etc): SELECT rolname FROM pg_roles WHERE rolname IN (SELECT member::regrole::text FROM pg_auth_members WHERE role::regrole::text LIKE '%replication%');Affected if Users without explicit replication duties hold replication privileges
-
Audit recent pglogical function executionsCheck pg_stat_statements or logs for executions of pglogical functions (pglogical.replication_set_add_table, pglogical.subscription_sync, etc) from unexpected session contextsAffected if pglogical functions were called by sessions that were not established via a replication connection
You are affected if pglogical 3.x, BDR/PGD 4, or BDR/PGD 5 is installed AND a database is configured for replication AND untrusted users have CONNECT access to that database.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedApply vendor patches when available. As an interim control, restrict CONNECT permissions on databases configured for replication to only trusted users and monitor for unauthorized replication connection attempts.
Obtain the fixed release from EDB - contact EDB Technical Support or check EDB security advisories at www.enterprisedb.com for the specific version numbers for pglogical 3.x, BDR 4, and PGD 5 that include the replication connection verification fix.
- Contact EDB Technical Support or visit www.enterprisedb.com to obtain the specific patch or updated release for pglogical 3.x, BDR 4, or PGD 5 that addresses CVE-2025-2506.
- Verify your current pglogical/BDR/PGD version by querying the database or checking installed packages.
- Apply the vendor-provided patch or upgrade to the fixed release as directed by EDB.
- After upgrade, verify that pglogical now properly validates replication connections before granting access to replicated data.
- Confirm the fix by testing that non-replication connections cannot execute pglogical replication commands.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing10.0 h
- Review / QA6.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $9,504.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2506 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-2506 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data