<?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 14:22:47 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-116248 — pgAdmin 4: Non-administrators can share a server with every user</title>
      <link>https://db.gcve.eu/vuln/cve-2026-116248</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; pgadmin.org pgAdmin 4&lt;/p&gt;
&lt;p&gt;In pgAdmin 4 server mode only administrators are meant to share a server with all users; the server dialog shows the Shared switch only to them. The create and update endpoints of the server API, however, stored the &amp;#34;shared&amp;#34; flag and shared username they were sent, so any user able to register a server could share one with every other user. The servers.json import had a similar gap: a non-administrator&amp;#39;s &amp;#34;Shared&amp;#34; entries were removed only after validation, so a file that also held an invalid entry could create a shared server.&lt;/p&gt;
&lt;p&gt;A shared server carries no credentials, so this gives no direct access. It lets a user plant a server, named to look trusted, in every other user&amp;#39;s tree and pointing at a host the user controls; anyone who then connects to it presents their own database password to that host.&lt;/p&gt;
&lt;p&gt;The fix refuses a non-administrator&amp;#39;s request that would share a server with HTTP 403, prunes a non-administrator&amp;#39;s shared entries from a servers.json import before validating it, and warns at startup about servers shared earlier by non-administrators.&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;In pgAdmin 4 server mode only administrators are meant to share a server with all users; the server dialog shows the Shared switch only to them. The create and update endpoints of the server API, however, stored the &amp;#34;shared&amp;#34; flag and shared username they were sent, so any user able to register a server could share one with every other user. The servers.json import had a similar gap: a non-administrator&amp;#39;s &amp;#34;Shared&amp;#34; entries were removed only after validation, so a file that also held an invalid entry could create a shared server.&lt;/p&gt;
&lt;p&gt;A shared server carries no credentials, so this gives no direct access. It lets a user plant a server, named to look trusted, in every other user&amp;#39;s tree and pointing at a host the user controls; anyone who then connects to it presents their own database password to that host.&lt;/p&gt;
&lt;p&gt;The fix refuses a non-administrator&amp;#39;s request that would share a server with HTTP 403, prunes a non-administrator&amp;#39;s shared entries from a servers.json import before validating it, and warns at startup about servers shared earlier by non-administrators.&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-116248</guid>
    </item>
  </channel>
</rss>
