A use-after-free condition exists in pglogical's worker signaling code, where a worker structure can be dereferenced after the underlying slot has been freed or recycled during normal worker lifecycle events. The condition is reachable during normal replication operation, including by a low-privileged user able to influence worker start, stop, and restart timing through permitted pglogical operations. In [truncated]
CVE-2026-50737 is a critical vulnerability in the pglogical extension for PostgreSQL, allowing a publisher to escalate privileges to superuser on a subscriber. The issue arises from pglogical's handling of replicated changes for rows missing one or more columns. When applying such changes, pglogical evaluates the affected table's default expressions on the subscriber. Since the apply worker operates at a [truncated]
The CVE-2026-50736 issue is a critical vulnerability in the pglogical extension for PostgreSQL. An attacker with publisher privileges can send crafted queue messages to execute arbitrary SQL as superuser on subscribers, breaking tenant isolation in shared deployments. This requires directing a subscription to a controlled endpoint, typically necessitating superuser privileges in default installations. The [truncated]
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-07-28T19:17:36.540Z and has not been modified since then. The NVD entry is currently Analyzed. The pglogical extension in PostgreSQL is vulnerable to an out-of-bounds read. The apply worker does not sufficiently validate the length of certain fields in incoming replication protocol messages before copy [truncated]
