# CVE-2025-2506: Missing authorization in BDR/PGD

> Users with CONNECT access can bypass replication checks to read replicated tables in pglogical and BDR/PGD environments.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 22 May 2025
- **Updated:** 26 Aug 2025

## What is CVE-2025-2506?

CVE-2025-2506 is a medium-severity missing authorization vulnerability in EnterpriseDB BDR/PGD, published on 22 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2025-2506?


## How do I fix CVE-2025-2506?

No fix has been published for CVE-2025-2506 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-2506 being exploited?

There is no known exploitation of CVE-2025-2506 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-2506 and fix it if it is affected.

What it is: CVE-2025-2506 is a medium-severity missing authorization vulnerability in EnterpriseDB BDR/PGD, published on 22 May 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-2506 in the wild and no public exploit code.

Affected product: EnterpriseDB BDR/PGD. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-2506/ (Markdown: https://insights.sbomify.com/CVE-2025-2506/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-2506
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-2506
- OSV: https://osv.dev/vulnerability/CVE-2025-2506

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-2506/
Summaries are generated and may contain mistakes; the official description above is the record.