Quick answers
- Is CVE-2026-50737 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50737 being exploited in the wild.
- How severe is CVE-2026-50737?
- Informational severity, with a CVSS score of 9, 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-50737?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-50737 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-50737?
- 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 privilege escalation vulnerability exists in pglogical when applying replicated changes for rows missing one or more columns. The subscriber's apply worker evaluates the table's default expressions at a privilege level equivalent to a PostgreSQL superuser. An attacker acting as a publisher can craft a replication stream that triggers these default expressions, executing arbitrary functions with superuser privileges. This attack requires the ability to direct a subscription to an attacker-controlled endpoint, a configuration typically restricted to superusers but often delegated in managed database environments. The issue is fixed in pglogical version 2.4.8.
Affected products
- EnterpriseDB pglogical 2.x before 2.4.8
Timeline
- 2026-07-28: disclosed
- 2026-07-28: advisory