Quick answers
- Is CVE-2026-50736 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50736 being exploited in the wild.
- How severe is CVE-2026-50736?
- 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-50736?
- 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-50736 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-50736?
- 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 the pglogical queue mechanism, which is used to replicate DDL and out-of-band commands. The root cause is that message payloads are executed on the subscriber using the 'apply worker' context, which typically operates with PostgreSQL superuser privileges. An attacker who can control a publisher or redirect a subscription to a malicious endpoint can send crafted queue messages to execute arbitrary SQL as a superuser. While this usually requires superuser privileges to set up in default installations, it poses a critical risk in managed environments where subscription management has been delegated to non-privileged roles. 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