CVE-2026-50737: Critical severity pglogical pglogical vulnerability
When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table's default expressions on the subscriber. Because the apply worker runs at a privilege level equivalent to a PostgreSQL superuser in default installations, any function invoked by such a default expression also runs at that privilege. A party acting as the publisher can use this path to cause functions to be executed on the subscriber as superuser, escalating from a role permitted to use pglogical to full superuser.
This is a second, independent path to the same superuser escalation tracked under CVE-2026-50736 (the pglogical queue issue). 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-50737?
The severity of CVE-2026-50737 is rated at 55.
How do I fix CVE-2026-50737?
To fix CVE-2026-50737, review and restrict the default expressions and functions used in the affected tables' subscriptions.
What systems are affected by CVE-2026-50737?
CVE-2026-50737 affects systems running pglogical in PostgreSQL.
What are the potential risks associated with CVE-2026-50737?
The risks associated with CVE-2026-50737 include unauthorized function execution due to elevated privileges of the apply worker.
When was CVE-2026-50737 published?
CVE-2026-50737 was published on July 28, 2026.