Vulnary
← back to the feed
Critical· 9

CVE-2026-50737

A flaw in PostgreSQL’s pglogical extension lets a publisher force a subscriber to run arbitrary functions as a superuser when replicating changes for a row that lacks one or more columns. The issue is a privilege‑escalation vulnerability that can give an attacker full control over the subscriber database.

publishedJul 28, 2026
last modifiedJul 28, 2026
sourcesNVD
severity · cvss
9
critical · how bad it is
exploitation · epss
<1%
9th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Sep 11, 2026

No official fix yet. If none appears within 45 days of first tracking, this entry is removed automatically.

01

Who is affected

PostgreSQL installations that use the pglogical extension, especially managed deployments where non‑superuser roles can create subscriptions.

02

Real-world impact

An attacker who can set up a subscription to a controlled endpoint can cause the subscriber to execute any function with superuser rights, potentially compromising the entire database and all data it holds.

03

Why this severity

The CVSS score of 9 reflects the high impact of gaining superuser privileges (confidentiality, integrity, and availability are all fully compromised) combined with the need for network access and a relatively high attack complexity. The score also accounts for the fact that the vulnerability is exploitable only when the attacker can create a subscription, which is typically restricted to privileged users.

04

What to do about it

no official fix yet
interim mitigations
  • Restrict the creation of pglogical subscriptions to superuser roles and avoid using default expressions that invoke privileged functions.

No official fix or mitigation is documented in the sources yet. Monitor the vendor advisory and apply the patch as soon as it is released.

No fix documented in sources

05

Timeline

06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityHigh
Attack requirementsPresent
Privileges requiredLow
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
CVE-2026-50737: A flaw in PostgreSQL’s pglogical extension lets a publisher force a su · Vulnary