# CVE-2026-50738: Use after free in pglogical

> A use-after-free in pglogical allows low-privileged users to crash replication workers or potentially execute remote code via worker lifecycle manipulation.

- **Severity:** High 7.7 (`CVSS:4.0/AV:N/AC:H/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-50738, ECHO-af9c-763e-6a2b, GHSA-7pcx-4vjw-f9pr, UBUNTU-CVE-2026-50738

## What is CVE-2026-50738?

CVE-2026-50738 is a high-severity use after free vulnerability in EnterpriseDB pglogical, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A use-after-free condition exists in pglogical's worker signaling code, where a worker structure can be dereferenced after the underlying slot has been freed or recycled during normal worker lifecycle events. The condition is reachable during normal replication operation, including by a low-privileged user able to influence worker start, stop, and restart timing through permitted pglogical operations. In the typical case the condition crashes replication workers, causing an availability impact. In the worst case a use-after-free in a PostgreSQL backend can be leveraged as a remote code execution primitive at the privilege of that backend.

Weakness: CWE-416 (Use After Free)

## Which versions are affected by CVE-2026-50738?

It affects 1 product.


Products: Enterprisedb Pglogical.

## How do I fix CVE-2026-50738?

Apply the vendor's patch.

## Is CVE-2026-50738 being exploited?

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

## Other vulnerabilities in EnterpriseDB pglogical

- [CVE-2026-50736](https://insights.sbomify.com/CVE-2026-50736/): SQL injection in pglogical (critical 9.0)
- [CVE-2026-50737](https://insights.sbomify.com/CVE-2026-50737/): Privilege escalation in pglogical (critical 9.0)
- [CVE-2026-50735](https://insights.sbomify.com/CVE-2026-50735/): Information disclosure in pglogical (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50738 and fix it if it is affected.

What it is: CVE-2026-50738 is a high-severity use after free vulnerability in EnterpriseDB pglogical, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50738 in the wild and no public exploit code.

Affected product: EnterpriseDB pglogical. 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-2026-50738/ (Markdown: https://insights.sbomify.com/CVE-2026-50738/index.md)
```

## Sources

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

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