CVE-2026-50736
HighCVSS 7.5Exploitation Probability (EPSS)
Low risk9th percentile - higher than 9% of all known CVEs
Summary
The pglogical queue mechanism executes message payloads on the subscriber with PostgreSQL superuser privileges. A publisher can send crafted messages to execute arbitrary SQL as superuser, escalating privileges and breaking tenant isolation.
Risk Assessment
An attacker with subscription creation privileges can gain full superuser control over the PostgreSQL instance, compromising data confidentiality and integrity, and potentially taking over the entire system.
Recommendation
Restrict pglogical subscription creation privileges to trusted roles only and consider using separate PostgreSQL instances for different tenants to enforce isolation.
Other vulnerabilities in pglogical
See all- CVE-2026-50738Medium
A use-after-free condition exists in pglogical's worker signaling code, where a worker structure can be dereferenced after the underlying slot has been freed or recycled during normal worker lifecycle events. The condition is reachable during normal replication operation, including by a low-privileged user able to influence worker start, stop, and restart timing through permitted pglogical operations. In the typical case the condition crashes replication workers, causing an availability impact. In the worst case a use-after-free in a PostgreSQL backend can be leveraged as a remote code execution primitive at the privilege of that backend.
- CVE-2026-50737High
In pglogical, when applying replicated changes for a row with missing columns, the table's default expressions are evaluated on the subscriber. The apply worker runs with PostgreSQL superuser privileges, so functions invoked by default expressions also run with those privileges. A publisher can use this path to escalate to superuser on the subscriber.
- CVE-2026-50735Medium
The apply worker in pglogical does not sufficiently validate field lengths in incoming replication protocol messages before copying them, leading to an out-of-bounds read. An attacker controlling a publishing endpoint can send crafted messages, causing disclosure of process memory or crashing the apply worker.
Original NVD description (English source)
The pglogical queue mechanism, used to convey out-of-band commands such as replicated DDL from a publisher to a subscriber, executes message payloads on the subscriber at the privilege level of the apply worker, which is equivalent to a PostgreSQL superuser in default installations. A party acting as the publisher can send crafted queue messages that cause arbitrary SQL to be executed on the subscriber as superuser, escalating from a role permitted to use pglogical to full superuser and breaking the isolation between tenants in shared deployments. 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 data from NVD (NIST) · CISA KEV · EPSS