Skip to content

CVE-2026-50735 pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting a...

MediumCVSS 6.1 EPSS 0.42%
Published
Updated
Exploit status
No public exploit known
CISA SSVC
No known exploitation · automatable: no · technical impact: partial
Technology
UbuntuDebian

Description

pglogical's apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copying them, resulting in an out-of-bounds read. A party acting as the publisher for a subscription, for example a non-PostgreSQL endpoint that speaks the pglogical replication protocol, can return crafted messages that cause the subscriber's apply worker to read beyond the bounds of an allocated buffer, disclosing adjacent process memory or crashing the worker. 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.

Upgrade path

9 packages: 3 fixed, 6 with no fix yet.

PackageAffectedFixed inStatus
debian/pglogical(Debian 12) = 2.4.2-3; = 2.4.3-1; = 2.4.3-2; = 2.4.4-1 +9 more No fix listed No fix yet
debian/pglogical(Debian 13) = 2.4.5-1; = 2.4.6-1; = 2.4.6-2; = 2.4.7-1 +3 more No fix listed No fix yet
ubuntu/pglogical(Ubuntu 22.04) All versions No fix listed No fix yet
ubuntu/pglogical(Ubuntu 24.04) All versions No fix listed No fix yet
ubuntu/pglogical(Ubuntu 26.04) All versions No fix listed No fix yet
ubuntu/pglogical(Ubuntu 26.10) All versions No fix listed No fix yet
debian/pglogical(Debian 14) < 2.4.8-1; = 2.4.5-1; = 2.4.6-1; = 2.4.6-2 +1 more 2.4.8-1 Fixed
EnterpriseDB pglogical >= 2, < 2.4.8; >= 2.0.0, < 2.4.8 2.4.8 Fixed
pgEdge Spock >= 3, <= 3.3.6; >= 4, <= 4.1.0.3; >= 5, <= 5.0.11 after 3.3.6, 4.1.0.3, 5.0.11 Fixed

Affected products

ProductAffected versionsFixed in
ubuntu/pglogical(Ubuntu:22.04) All versions No fix listed
ubuntu/pglogical(Ubuntu:24.04) All versions No fix listed
ubuntu/pglogical(Ubuntu:26.04) All versions No fix listed
ubuntu/pglogical(Ubuntu:26.10) All versions No fix listed
debian/pglogical(Debian:12) All versions No fix listed
debian/pglogical(Debian:14) < 2.4.8-1 2.4.8-1
debian/pglogical(Debian:13) All versions No fix listed
EnterpriseDB pglogical >= 2, < 2.4.8 2.4.8
pgEdge Spock >= 3, <= 3.3.6 No fix listed
pgEdge Spock >= 4, <= 4.1.0.3 No fix listed
pgEdge Spock >= 5, <= 5.0.11 No fix listed
EnterpriseDB pglogical >= 2.0.0, < 2.4.8 2.4.8
debian/pglogical(Debian:12) = 2.4.2-3 No fix listed
debian/pglogical(Debian:12) = 2.4.3-1 No fix listed
debian/pglogical(Debian:12) = 2.4.3-2 No fix listed
debian/pglogical(Debian:12) = 2.4.4-1 No fix listed
debian/pglogical(Debian:12) = 2.4.4-2 No fix listed
debian/pglogical(Debian:12) = 2.4.4-3 No fix listed
debian/pglogical(Debian:12) = 2.4.5-1 No fix listed
debian/pglogical(Debian:12) = 2.4.6-1 No fix listed
debian/pglogical(Debian:12) = 2.4.6-2 No fix listed
debian/pglogical(Debian:12) = 2.4.7-1 No fix listed
debian/pglogical(Debian:12) = 2.4.8-1 No fix listed
debian/pglogical(Debian:12) = 2.4.8-2 No fix listed
debian/pglogical(Debian:13) = 2.4.5-1 No fix listed
Show 9 more
ProductAffected versionsFixed in
debian/pglogical(Debian:13) = 2.4.6-1 No fix listed
debian/pglogical(Debian:13) = 2.4.6-2 No fix listed
debian/pglogical(Debian:13) = 2.4.7-1 No fix listed
debian/pglogical(Debian:13) = 2.4.8-1 No fix listed
debian/pglogical(Debian:13) = 2.4.8-2 No fix listed
debian/pglogical(Debian:14) = 2.4.5-1 No fix listed
debian/pglogical(Debian:14) = 2.4.6-1 No fix listed
debian/pglogical(Debian:14) = 2.4.6-2 No fix listed
debian/pglogical(Debian:14) = 2.4.7-1 No fix listed

References