# CVE-2026-50737

## Summary

- **CVE ID:** CVE-2026-50737
- **Severity:** CRITICAL
- **CVSS Score:** 9 (CVSS:4.0/AV:N/AC:H/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H)
- **CWE:** CWE-250
- **Published:** Jul 28, 2026
- **Last Modified:** Jul 28, 2026

## Description

When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table's default expressions on the subscriber. Because the apply worker runs at a privilege level equivalent to a PostgreSQL superuser in default installations, any function invoked by such a default expression also runs at that privilege. A party acting as the publisher can use this path to cause functions to be executed on the subscriber as superuser, escalating from a role permitted to use pglogical to full superuser.

This is a second, independent path to the same superuser escalation tracked under CVE-2026-50736 (the pglogical queue issue). 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 Products

- EnterpriseDB — pglogical (2)

## References

- [CNA](https://www.enterprisedb.com/docs/security/advisories/cve202650737/)

## Exploitation Prediction (EPSS)

- **EPSS Score:** 0.24%
- **EPSS Percentile:** 14.4

---
_Exported from OnDuty AI Vulnerability Intelligence on 2026-09-10._