CVE-2026-50736
pglogical allows publisher messages to execute arbitrary superuser SQL on subscribers
Is CVE-2026-50736 being exploited?
Not confirmed. CVE-2026-50736 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.24% probability of exploitation in the next 30 days.
How severe is CVE-2026-50736?
CVE-2026-50736 is rated Critical with a CVSS score of 9.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-50736?
Yes. A fix has been recorded for CVE-2026-50736. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-50736 affect?
CVE-2026-50736 affects PostgreSQL (with pglogical extension), pglogical apply worker / queue mechanism, Managed/multi-tenant PostgreSQL hosting with delegated subscription creation. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-50736?
Restrict subscription creation to superusers, block/untrust publishers, disable pglogical in multi-tenant hosts; apply vendor patch when released.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
An attacker controlling a publisher endpoint can run arbitrary SQL as PostgreSQL superuser on a subscriber, achieving full privilege escalation and breaking tenant isolation.
Immediate action required
- affected>= 2 and < 2.4.8
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.