Description
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.
Published: 2026-07-28
Score: 9 Critical
EPSS: < 1% Very Low
KEV: No
Impact: n/a
Action: n/a
AI Analysis

Impact

A flaw in pglogical causes replica changes to trigger default expressions on the subscriber when a row is missing columns. The apply worker operates at superuser privilege on the subscriber, so any function called by the default expression also runs as superuser. An attacker who can control the publisher can exploit this to execute arbitrary functions on the subscriber with full superuser rights, effectively escalating from a pglogical‑permitted role to a superuser. This is a classic privilege‑escalation issue (CWE‑250).

Affected Systems

The vulnerability affects EnterpriseDB pglogical. It is relevant to deployments where non‑superuser roles are granted permission to create subscriptions, which is typical in managed database services. No specific affected versions are listed.

Risk and Exploitability

The CVSS score of 9 indicates high severity, yet the EPSS score is less than 1%, reflecting a low likelihood of exploitation in the wild. The issue is not listed in the CISA KEV catalog. Exploitation requires the attacker to act as the publisher and create a subscription pointing to an endpoint they control. In default installations, this requires superuser privileges to create subscriptions, so the risk is highest in managed setups that delegate subscription creation to lower‑privileged roles. The attack vector is therefore limited to scenarios where a non‑superuser can publish to a subscriber they govern.

Generated by OpenCVE AI on August 4, 2026 at 12:53 UTC.

Remediation

No vendor fix or workaround currently provided.

OpenCVE Recommended Actions

  • Apply the vendor‑issued patch that fixes pglogical default expression handling.
  • Revoke or restrict the ability of non‑superuser roles to create pglogical subscriptions, limiting subscription creation to superuser accounts.
  • If a patch is unavailable, disable default expression evaluation on subscriber tables or enforce safe default expressions that do not call privileged functions.

Generated by OpenCVE AI on August 4, 2026 at 12:53 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Tue, 04 Aug 2026 13:15:00 +0000

Type Values Removed Values Added
Title Superuser Escalation via pglogical Default Expression Execution

Sun, 02 Aug 2026 09:15:00 +0000

Type Values Removed Values Added
Title Superuser Escalation via pglogical Default Expression Execution

Wed, 29 Jul 2026 20:30:00 +0000

Type Values Removed Values Added
Metrics ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'total'}, 'version': '2.0.3'}


Tue, 28 Jul 2026 21:00:00 +0000

Type Values Removed Values Added
First Time appeared Enterprisedb
Enterprisedb pglogical
Vendors & Products Enterprisedb
Enterprisedb pglogical

Tue, 28 Jul 2026 18:30:00 +0000

Type Values Removed Values Added
Description 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.
Weaknesses CWE-250
References
Metrics cvssV4_0

{'score': 9, 'vector': 'CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H'}


Subscriptions

Enterprisedb Pglogical
cve-icon MITRE

Status: PUBLISHED

Assigner: EDB

Published:

Updated: 2026-07-28T18:52:19.292Z

Reserved: 2026-06-05T19:13:51.103Z

Link: CVE-2026-50737

cve-icon Vulnrichment

Updated: 2026-07-28T18:52:12.709Z

cve-icon NVD

Status : Awaiting Analysis

Published: 2026-07-28T19:17:36.827

Modified: 2026-07-30T16:31:26.770

Link: CVE-2026-50737

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-08-04T13:00:11Z

Weaknesses
  • CWE-250

    Execution with Unnecessary Privileges