CVE-2026-50736: SQL Injection

Published Jul 28, 2026
·
Updated

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.

Affected Software

2 affected components
pglogical pglogical
EnterpriseDB Pglogical Postgresql>=2.0.0<2.4.8

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Compensating control

    For shared/managed deployments, prevent delegated (non-superuser) roles from directing pglogical subscriptions at endpoints they control; restrict who can create subscriptions and where they may point to so an attacker cannot direct a subscription at an endpoint they control.

  2. Compensating control

    Isolate and strictly control network access for pglogical publisher/subscriber endpoints so that only authorized subscribers can receive pglogical queue messages (limit exposure of subscriber endpoints to untrusted parties).

Event History

Jul 28, 2026
CVE Published
via MITRE·05:55 PM
Data Sourced
via MITRE·05:55 PM
DescriptionWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2026-50736?

CVE-2026-50736 has a risk rating of 60, indicating a moderate security vulnerability.

2

How do I fix CVE-2026-50736?

To fix CVE-2026-50736, ensure that pglogical is updated to its latest version where the vulnerability is addressed.

3

What systems are affected by CVE-2026-50736?

CVE-2026-50736 affects PostgreSQL installations using the pglogical extension.

4

What are the potential impacts of CVE-2026-50736?

The vulnerability may allow unauthorized execution of commands at superuser privilege levels on the subscriber.

5

Is CVE-2026-50736 an SQL injection vulnerability?

Yes, CVE-2026-50736 is categorized under SQL Injection vulnerabilities.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203