Vulnerability Details CVE-2026-50737
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.
Exploit prediction scoring system (EPSS) score
EPSS Score 0.002
EPSS Ranking 9.1%
CVSS Severity
CVSS v3 Score 7.5
Products affected by CVE-2026-50737
-
cpe:2.3:a:enterprisedb:pglogical:2.0.0
-
cpe:2.3:a:enterprisedb:pglogical:2.0.1
-
cpe:2.3:a:enterprisedb:pglogical:2.1.0
-
cpe:2.3:a:enterprisedb:pglogical:2.1.1
-
cpe:2.3:a:enterprisedb:pglogical:2.2.0
-
cpe:2.3:a:enterprisedb:pglogical:2.2.1
-
cpe:2.3:a:enterprisedb:pglogical:2.2.2
-
cpe:2.3:a:enterprisedb:pglogical:2.3.0
-
cpe:2.3:a:enterprisedb:pglogical:2.3.1
-
cpe:2.3:a:enterprisedb:pglogical:2.3.2
-
cpe:2.3:a:enterprisedb:pglogical:2.3.3
-
cpe:2.3:a:enterprisedb:pglogical:2.3.4
-
cpe:2.3:a:enterprisedb:pglogical:2.4.0
-
cpe:2.3:a:enterprisedb:pglogical:2.4.1
-
cpe:2.3:a:enterprisedb:pglogical:2.4.2
-
cpe:2.3:a:enterprisedb:pglogical:2.4.3
-
cpe:2.3:a:enterprisedb:pglogical:2.4.4
-
cpe:2.3:a:enterprisedb:pglogical:2.4.5
-
cpe:2.3:a:enterprisedb:pglogical:2.4.6
-
cpe:2.3:a:enterprisedb:pglogical:2.4.7