CVE-2026-50736 EnterpriseDB CVE debrief

Who should care

PostgreSQL administrators and users of the pglogical extension, especially those in managed environments where non-superuser roles have been delegated subscription creation privileges.

Technical summary

The pglogical extension for PostgreSQL is vulnerable to a critical issue (CVE-2026-50736) where an attacker with publisher privileges can send crafted queue messages to execute arbitrary SQL as superuser on subscribers. This breaks tenant isolation in shared deployments and requires directing a subscription to a controlled endpoint, typically necessitating superuser privileges in default installations.

Defensive priority

This vulnerability allows for privilege escalation in PostgreSQL deployments using the pglogical extension, particularly in managed environments where subscription creation has been delegated to non-superuser roles.

Recommended defensive actions

• Review and restrict subscription creation privileges to trusted roles.
• Implement strict access controls for pglogical publishers and subscribers.
• Monitor for suspicious activity in PostgreSQL logs related to pglogical operations.
• Apply the vendor's patch or upgrade to a fixed version of pglogical.
• Conduct regular security audits of PostgreSQL and pglogical configurations.

Evidence notes

The CVE-2026-50736 issue arises from the pglogical queue mechanism, which executes message payloads at the privilege level of the apply worker, equivalent to a PostgreSQL superuser. An attacker with publisher privileges can send crafted messages to execute arbitrary SQL as superuser on subscribers, breaking tenant isolation in shared deployments. Exploitation requires directing a subscription to a controlled endpoint, typically requiring superuser privileges in default installations.

Official resources