External risk intelligence

pglogical Replication Default Expression Superuser Escalation

CVE advisorySeverity: CRITICAL (CVSS 9.0)

CVE-2026-50737

The vulnerability affects pglogical replication subscriptions. This requires a complex, internal-facing configuration where a subscriber connects to a publisher. While network-reachable, it is typically restricted to database administration workflows, requires specific privileges to configure, and is not a public-facing service or internet-exposed endpoint in standard deployments.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This advisory concerns a critical vulnerability in pglogical, a PostgreSQL replication tool, that could allow a malicious party to execute arbitrary commands with superuser privileges on a subscriber system. This occurs when replicated changes are applied to a table missing columns, causing default expressions to run with elevated permissions. While complex to exploit, it represents a significant risk if non-superuser roles have been delegated subscription management privileges in managed deployments.

  • Elevated privileges possible through replication changes.
  • Critical for managed deployments with delegated permissions.
  • Confirm relevance and exposure; mitigate if necessary.

Attack Path

How an attacker could exploit the issue

An attacker with publisher privileges could manipulate data replication to execute arbitrary functions on a subscriber's database. This is achieved by creating a subscription to an endpoint they control and causing the system to evaluate default expressions with missing columns, which then triggers functions to run with elevated privileges. In typical setups, this capability is restricted to superusers, but in managed environments where non-superusers can create subscriptions, this opens a path for privilege escalation.

  • Requires control over a subscription endpoint.
  • Triggered by replicating rows with missing columns.
  • Leads to arbitrary code execution as superuser.

Live Threat

Current exploitation, exposure, and threat context

This vulnerability could allow a malicious publisher to execute arbitrary functions as a superuser on a subscriber system. This could happen when changes are replicated for a row with missing columns and the subscriber evaluates default expressions that invoke these functions. The risk is heightened in managed deployments where non-superusers are delegated the ability to create subscriptions.

  • Attacker-controlled subscription endpoints.
  • Replication of rows with missing columns.
  • Full superuser access on subscriber.

Operational Fix

Recommended remediation, mitigation, and detection steps

This critical vulnerability allows a publisher to execute arbitrary functions on a subscriber with superuser privileges, primarily impacting managed PostgreSQL deployments where subscription creation is delegated. The first practical step is to identify all pglogical subscriptions, assess their reachability to controlled endpoints, confirm business criticality, and identify the accountable database or platform team. Remediation planning should then be risk-based, considering potential vendor coordination or temporary risk reduction strategies.

  • Database and Platform teams own this issue.
  • Verify pglogical subscription configurations.
  • Plan remediation based on risk.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is pglogical and how is it used?

pglogical is an extension for PostgreSQL designed for logical replication. It allows data to be copied and synchronized between separate database instances. It is widely used by database administrators to move data between different versions of PostgreSQL, set up complex replication topologies, or perform migrations where standard physical streaming replication is not suitable.

What kind of vulnerability is CVE-2026-50737?

This CVE involves a weakness classified as CWE-250, which relates to Execution with Unnecessary Privileges. In this specific scenario, the pglogical replication worker runs with superuser-level permissions. When the system encounters certain data anomalies during replication, it inadvertently triggers database functions with those same high-level privileges, effectively allowing code execution with full administrative power.

What steps are required to trigger this vulnerability?

An attacker must be able to influence the replication process by directing a subscriber database to connect to a publisher endpoint they control. The flaw is triggered when this controlled publisher sends data for a row that is missing expected columns, forcing the subscriber to evaluate default expressions. Simply having a standard replication setup does not trigger this; the attacker must control the publisher and the specific data structure being replicated.

How relevant is CVE-2026-50737 to my infrastructure?

Halo Surface Signal indicates this is unlikely to be a direct internet-exposed risk because it involves complex database-to-database replication workflows. The vulnerability is most relevant to managed environments where subscription creation has been delegated to non-administrative users. If your database configuration restricts subscription management solely to trusted superusers, the practical path for an attacker to reach this flaw is significantly reduced.

How should I respond if I am running pglogical?

Begin by auditing your current pglogical setup to identify all existing subscriptions and verify who holds the permissions to create them. Coordinate with your database and platform teams to confirm if any non-privileged users have been granted the ability to manage these connections. Once you have identified these configurations, assess the risk level and plan your remediation steps accordingly.