# CVE-2026-50737: Privilege escalation in pglogical

> A malicious publisher can execute arbitrary functions as superuser on a pglogical subscriber by exploiting default expression evaluation during row replication.

- **Severity:** Critical 9.0 (`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`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 28 Jul 2026
- **Updated:** 28 Jul 2026
- **Also known as:** DEBIAN-CVE-2026-50737, ECHO-2055-6c03-d4b2, GHSA-h7hw-g87c-29wh, UBUNTU-CVE-2026-50737

## What is CVE-2026-50737?

CVE-2026-50737 is a critical vulnerability in EnterpriseDB pglogical, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official 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.

Weakness: CWE-250 (Execution with Unnecessary Privileges)

## Which versions are affected by CVE-2026-50737?

It affects 1 product.


Products: Enterprisedb Pglogical.

## How do I fix CVE-2026-50737?

Apply the vendor's patch.

## Is CVE-2026-50737 being exploited?

There is no known exploitation of CVE-2026-50737 in the wild and no public exploit code.

## Other vulnerabilities in EnterpriseDB pglogical

- [CVE-2026-50736](https://insights.sbomify.com/CVE-2026-50736/): SQL injection in pglogical (critical 9.0)
- [CVE-2026-50738](https://insights.sbomify.com/CVE-2026-50738/): Use after free in pglogical (high 7.7)
- [CVE-2026-50735](https://insights.sbomify.com/CVE-2026-50735/): Information disclosure in pglogical (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-50737 and fix it if it is affected.

What it is: CVE-2026-50737 is a critical vulnerability in EnterpriseDB pglogical, published on 28 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-50737 in the wild and no public exploit code.

Affected product: EnterpriseDB pglogical. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-50737/ (Markdown: https://insights.sbomify.com/CVE-2026-50737/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-50737
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-50737
- OSV: https://osv.dev/vulnerability/CVE-2026-50737

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-50737/
Summaries are generated and may contain mistakes; the official description above is the record.