CVE-2026-50735 - pglogical apply worker out-of-bounds read may disclose memory

First Published: 2026/07/28

Last Updated: 2026/07/28

Summary

pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting as the publisher for a subscription, for example a non-PostgreSQL endpoint that speaks the pglogical replication protocol, can return crafted messages that cause the subscriber's apply worker to read beyond the bounds of an allocated buffer, disclosing adjacent process memory or crashing the worker.

To exploit the issue an attacker must be able to direct a subscription at an endpoint they control. In default installations this requires privileges normally reserved for a superuser, so the issue is most relevant to managed deployments where the ability to create subscriptions has been delegated to non-superuser roles.

Vulnerability details

CVE-ID: CVE-2026-50735

CVSS Base Score: 6.1

CVSS Temporal Score: Undefined

CVSS Environmental Score: Undefined

CVSS Vector: CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:N/VA:H/SC:N/SI:N/SA:N

Affected products and versions

  • Affected Product: pglogical
  • Affected Versions: All versions of pglogical 2.x prior to 2.4.8

Remediation/fixes

Impacted users must upgrade to a fixed version of pglogical. A fix will be made available in the next release of pglogical 2.

ProductVRMFRemediation/First Fix
pglogicalAll 2.x versions prior to 2.4.8Update to latest supported version
(at least 2.4.8)

References

Acknowledgement

Source: Reported to EDB by Mehmet Ince (@mdisec) through the EDB Vulnerability Disclosure Program.

Change history

  • 2026/07/28: Original Copy Published

Disclaimer

This document is provided on an "as is" basis and does not imply any kind of guarantee or warranty, including the warranties of merchantability or fitness for a particular use. Your use of the information on the document is at your own risk. EDB reserves the right to change or update this document at any time. Customers are therefore recommended to always view the latest version of this document.


Could this page be better? Report a problem or suggest an addition!