Quick answers
- Is CVE-2026-50738 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50738 being exploited in the wild.
- How severe is CVE-2026-50738?
- Informational severity, with a CVSS score of 7.7, published 28 July 2026.
- Which products and versions are affected?
- EnterpriseDB Pglogical 2.x before 2.4.8.
- Is there a fix for CVE-2026-50738?
- A patch was published on 2026-07-28: Fix released in version 2.4.8 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-50738 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-50738?
- Check whether you run EnterpriseDB Pglogical at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A use-after-free (CWE-416) vulnerability exists in the worker signaling component of pglogical. The flaw occurs when a worker structure is dereferenced after its associated slot has been freed or recycled during lifecycle events (start, stop, or restart). An attacker with low privileges can trigger this condition by manipulating the timing of these worker operations. While the most common outcome is a denial-of-service (DoS) via worker crashes, the memory corruption could potentially be exploited for remote code execution (RCE) within the context of the PostgreSQL backend process. The issue is addressed in pglogical version 2.4.8.
Affected products
- EnterpriseDB pglogical 2.x before 2.4.8
Timeline
- 2026-07-28: advisory: Initial disclosure by EnterpriseDB
- 2026-07-28: patched: Fix released in version 2.4.8