Quick answers
- Is CVE-2026-50735 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-50735 being exploited in the wild.
- How severe is CVE-2026-50735?
- Informational severity, with a CVSS score of 6.1, 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-50735?
- 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-50735 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-50735?
- 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
An out-of-bounds read vulnerability (CWE-125) exists in the pglogical apply worker due to insufficient validation of field lengths in incoming replication protocol messages. An attacker acting as a replication publisher can send crafted messages that cause the subscriber's apply worker to read beyond allocated buffer bounds. This can lead to the disclosure of adjacent process memory or a denial-of-service condition via worker crashes. Exploitation requires the attacker to control a replication endpoint and have the privileges necessary to direct a subscription to that endpoint (typically superuser, or delegated subscription roles in managed 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