CVE-2026-50737

published 28 Jul 2026 · updated 28 Jul 2026

When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table's default…

9.0CriticalCVSS 9.0EPSS 0%

No exploitation in the wild has been reported. EPSS puts the chance of exploitation in the next 30 days at 0%. Fixed in 2.4.8.

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

Vendors, products and packages with version ranges

VendorProductVersionsFixed
EnterpriseDB>=2 <2.4.82.4.8

Timeline

Every event on this vulnerability

Embed

A live severity badge for an advisory, README or ticket

CVE-2026-50737 severity on Zeptric[![CVE-2026-50737](https://zeptric.io/badge/cve/CVE-2026-50737.svg)](https://zeptric.io/cve/CVE-2026-50737)