CVE-2026-50735: Medium severity pglogical pglogical vulnerability
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.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-50735?
CVE-2026-50735 has a risk rating of 27.
How do I fix CVE-2026-50735?
To fix CVE-2026-50735, update to the latest version of pglogical that addresses this vulnerability.
What impact does CVE-2026-50735 have on my system?
CVE-2026-50735 can lead to an out-of-bounds read, potentially allowing for information leakage.
Who is affected by CVE-2026-50735?
CVE-2026-50735 affects systems using pglogical where a non-PostgreSQL endpoint acts as the publisher for a subscription.
What is pglogical in relation to CVE-2026-50735?
pglogical is a PostgreSQL extension that allows for logical replication, and CVE-2026-50735 highlights a vulnerability in its apply worker's handling of replication protocol messages.