<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://db.gcve.eu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Sun, 01 Nov 2026 22:52:05 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-116252 — pgAdmin 4: Materialized view refresh redirects its connection through a crafted database name</title>
      <link>https://db.gcve.eu/vuln/cve-2026-116252</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pgadmin.org pgAdmin 4&lt;/p&gt;
&lt;p&gt;pgAdmin 4&amp;#39;s materialized view refresh passed the target database&amp;#39;s name to psql&amp;#39;s --dbname argument unchanged. libpq treats a --dbname value containing &amp;#34;=&amp;#34; (or a postgresql:// URI) as a full connection string, whose keywords override the host, port and other settings pgAdmin had supplied. A database whose name is such a string, which any role with CREATEDB can create, therefore redirected the psql process pgAdmin starts for the refresh to a host and port of the creator&amp;#39;s choosing, and the connecting user&amp;#39;s saved server password was presented to that endpoint. It also let the pgAdmin host be made to open connections to arbitrary addresses.&lt;/p&gt;
&lt;p&gt;The same weakness was fixed for Backup, Restore, Maintenance and Import/Export Data in earlier releases (CVE-2026-86862); the materialized view refresh was the remaining caller. The fix routes the name through the same database_conninfo() helper, so libpq treats it strictly as a database name.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pgadmin.org pgAdmin 4&lt;/p&gt;
&lt;p&gt;pgAdmin 4&amp;#39;s materialized view refresh passed the target database&amp;#39;s name to psql&amp;#39;s --dbname argument unchanged. libpq treats a --dbname value containing &amp;#34;=&amp;#34; (or a postgresql:// URI) as a full connection string, whose keywords override the host, port and other settings pgAdmin had supplied. A database whose name is such a string, which any role with CREATEDB can create, therefore redirected the psql process pgAdmin starts for the refresh to a host and port of the creator&amp;#39;s choosing, and the connecting user&amp;#39;s saved server password was presented to that endpoint. It also let the pgAdmin host be made to open connections to arbitrary addresses.&lt;/p&gt;
&lt;p&gt;The same weakness was fixed for Backup, Restore, Maintenance and Import/Export Data in earlier releases (CVE-2026-86862); the materialized view refresh was the remaining caller. The fix routes the name through the same database_conninfo() helper, so libpq treats it strictly as a database name.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://db.gcve.eu/vuln/cve-2026-116252</guid>
    </item>
  </channel>
</rss>
