pglogical — security advisory
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.
- Products
- pglogical
- Affected versions
- 2.4.2-3, 2.4.3-1, 2.4.3-2, 2.4.4-1, 2.4.4-2, 2.4.4-3, 2.4.5-1, 2.4.6-1, 2.4.6-2, 2.4.7-1, 2.4.8-1, 2.4.8-2
- Fixed versions
- 2.4.8-1
- CVEs
- CVE-2026-50737
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 1 Nov 2026, 04:11 UTC · Revision 1
Source evidence
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.
osv:DEBIAN-CVE-2026-50737
pglogical
Fixed versions: Not specified
pglogical
Fixed versions: Not specified
pglogical
Fixed versions: 2.4.8-1
Complete source record
{
"id": "2e60d477e1c97809d374aa3798098f21c25b175919818059835d2ab730aebeed",
"url": "https://osv.dev/vulnerability/DEBIAN-CVE-2026-50737",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "DEBIAN-CVE-2026-50737",
"summary": "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.",
"evidence": "osv:DEBIAN-CVE-2026-50737",
"products": [
{
"name": {
"value": "pglogical",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "2.4.2-3",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.3-1",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.3-2",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.4-1",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.4-2",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.4-3",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.5-1",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.6-1",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.6-2",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.7-1",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.8-1",
"evidence": "/affected/0/versions"
},
{
"value": "2.4.8-2",
"evidence": "/affected/0/versions"
}
]
},
{
"name": {
"value": "pglogical",
"evidence": "/affected/1/package/name"
},
"prerequisites": [],
"fixed_versions": [],
"affected_versions": [
{
"value": "2.4.5-1",
"evidence": "/affected/1/versions"
},
{
"value": "2.4.6-1",
"evidence": "/affected/1/versions"
},
{
"value": "2.4.6-2",
"evidence": "/affected/1/versions"
},
{
"value": "2.4.7-1",
"evidence": "/affected/1/versions"
},
{
"value": "2.4.8-1",
"evidence": "/affected/1/versions"
},
{
"value": "2.4.8-2",
"evidence": "/affected/1/versions"
}
]
},
{
"name": {
"value": "pglogical",
"evidence": "/affected/2/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "2.4.8-1",
"evidence": "/affected/2/ranges"
}
],
"affected_versions": [
{
"value": "2.4.5-1",
"evidence": "/affected/2/versions"
},
{
"value": "2.4.6-1",
"evidence": "/affected/2/versions"
},
{
"value": "2.4.6-2",
"evidence": "/affected/2/versions"
},
{
"value": "2.4.7-1",
"evidence": "/affected/2/versions"
}
]
}
],
"severity": "high",
"structured": {
"id": "DEBIAN-CVE-2026-50737",
"aliases": [
"DEBIAN-CVE-2026-50737"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H"
}
],
"affected": [
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "pglogical",
"purl": "pkg:deb/debian/pglogical?arch=source&distro=bookworm",
"ecosystem": "Debian:12"
},
"versions": [
"2.4.2-3",
"2.4.3-1",
"2.4.3-2",
"2.4.4-1",
"2.4.4-2",
"2.4.4-3",
"2.4.5-1",
"2.4.6-1",
"2.4.6-2",
"2.4.7-1",
"2.4.8-1",
"2.4.8-2"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-50737.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
}
]
}
],
"package": {
"name": "pglogical",
"purl": "pkg:deb/debian/pglogical?arch=source&distro=trixie",
"ecosystem": "Debian:13"
},
"versions": [
"2.4.5-1",
"2.4.6-1",
"2.4.6-2",
"2.4.7-1",
"2.4.8-1",
"2.4.8-2"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-50737.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
},
{
"ranges": [
{
"type": "ECOSYSTEM",
"events": [
{
"introduced": "0"
},
{
"fixed": "2.4.8-1"
}
]
}
],
"package": {
"name": "pglogical",
"purl": "pkg:deb/debian/pglogical?arch=source&distro=forky",
"ecosystem": "Debian:14"
},
"versions": [
"2.4.5-1",
"2.4.6-1",
"2.4.6-2",
"2.4.7-1"
],
"database_specific": {
"source": "https://storage.googleapis.com/debian-osv/debian-cve-osv/DEBIAN-CVE-2026-50737.json"
},
"ecosystem_specific": {
"urgency": "not yet assigned"
}
}
],
"modified": "2026-10-24T10:01:09.416452335Z",
"provider": "osv",
"upstream": [
"CVE-2026-50737"
],
"references": [
"https://security-tracker.debian.org/tracker/CVE-2026-50737"
]
},
"related_cves": [
{
"value": "CVE-2026-50737",
"evidence": "/upstream"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 429071,
"published_at": "2026-07-28T19:17:36.827+00:00"
}