https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Fri, 02 Oct 2026 20:42:36 +0000 https://cve.radiocsirt.org/vuln/euvd-2026-342184 EUVD-2026-342184 https://cve.radiocsirt.org/vuln/euvd-2026-342184 https://cve.radiocsirt.org/vuln/fkie_cve-2026-50737 <p>When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table&#39;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.</p> <p>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.</p> <p>When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table&#39;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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/fkie_cve-2026-50737 https://cve.radiocsirt.org/vuln/ghsa-h7hw-g87c-29wh <p>When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table&#39;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.</p> <p>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.</p> <p>When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table&#39;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.</p> <p>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.</p> https://cve.radiocsirt.org/vuln/ghsa-h7hw-g87c-29wh https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-50737 <p><strong>Affected:</strong> Ubuntu:18.04:LTS: pglogical, Ubuntu:20.04:LTS: pglogical, Ubuntu:22.04:LTS: pglogical, Ubuntu:24.04:LTS: pglogical, Ubuntu:26.04:LTS: pglogical</p> <p>When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table&#39;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.</p> <p><strong>Affected:</strong> Ubuntu:18.04:LTS: pglogical, Ubuntu:20.04:LTS: pglogical, Ubuntu:22.04:LTS: pglogical, Ubuntu:24.04:LTS: pglogical, Ubuntu:26.04:LTS: pglogical</p> <p>When applying replicated changes for a row that is missing one or more columns, pglogical evaluates the affected table&#39;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.</p> https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-50737