<?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 09:32:07 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-116242</title>
      <link>https://db.gcve.eu/vuln/fkie_cve-2026-116242</link>
      <description>&lt;p&gt;pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file, so it always loaded the unencrypted private keys in ~/.ssh of the operating-system account running pgAdmin, read that account&amp;#39;s ~/.ssh/config (IdentityFile, User, HostName, ProxyCommand) for the tunnel host, and could use its ssh-agent. In server mode any user could therefore configure a tunnel to a host that accepts the service account&amp;#39;s key, with no credentials of their own or with an identity file that did not exist in their storage, and reach it as that account.&lt;/p&gt;
&lt;p&gt;The fix makes tunnels in server mode use only the identity file or password the user configured: the service account&amp;#39;s keys, configuration and agent are no longer used, and an identity file that cannot be found in the user&amp;#39;s storage is reported instead of falling back to ~/.ssh. Desktop mode is unchanged.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file, so it always loaded the unencrypted private keys in ~/.ssh of the operating-system account running pgAdmin, read that account&amp;#39;s ~/.ssh/config (IdentityFile, User, HostName, ProxyCommand) for the tunnel host, and could use its ssh-agent. In server mode any user could therefore configure a tunnel to a host that accepts the service account&amp;#39;s key, with no credentials of their own or with an identity file that did not exist in their storage, and reach it as that account.&lt;/p&gt;
&lt;p&gt;The fix makes tunnels in server mode use only the identity file or password the user configured: the service account&amp;#39;s keys, configuration and agent are no longer used, and an identity file that cannot be found in the user&amp;#39;s storage is reported instead of falling back to ~/.ssh. Desktop mode is unchanged.&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/fkie_cve-2026-116242</guid>
    </item>
    <item>
      <title>GHSA-949g-5qqm-q7xc</title>
      <link>https://db.gcve.eu/vuln/ghsa-949g-5qqm-q7xc</link>
      <description>&lt;p&gt;pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file, so it always loaded the unencrypted private keys in ~/.ssh of the operating-system account running pgAdmin, read that account&amp;#39;s ~/.ssh/config (IdentityFile, User, HostName, ProxyCommand) for the tunnel host, and could use its ssh-agent. In server mode any user could therefore configure a tunnel to a host that accepts the service account&amp;#39;s key, with no credentials of their own or with an identity file that did not exist in their storage, and reach it as that account.&lt;/p&gt;
&lt;p&gt;The fix makes tunnels in server mode use only the identity file or password the user configured: the service account&amp;#39;s keys, configuration and agent are no longer used, and an identity file that cannot be found in the user&amp;#39;s storage is reported instead of falling back to ~/.ssh. Desktop mode is unchanged.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;pgAdmin 4 opens SSH tunnels with the sshtunnel library but gave it neither host_pkey_directories nor ssh_config_file, so it always loaded the unencrypted private keys in ~/.ssh of the operating-system account running pgAdmin, read that account&amp;#39;s ~/.ssh/config (IdentityFile, User, HostName, ProxyCommand) for the tunnel host, and could use its ssh-agent. In server mode any user could therefore configure a tunnel to a host that accepts the service account&amp;#39;s key, with no credentials of their own or with an identity file that did not exist in their storage, and reach it as that account.&lt;/p&gt;
&lt;p&gt;The fix makes tunnels in server mode use only the identity file or password the user configured: the service account&amp;#39;s keys, configuration and agent are no longer used, and an identity file that cannot be found in the user&amp;#39;s storage is reported instead of falling back to ~/.ssh. Desktop mode is unchanged.&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/ghsa-949g-5qqm-q7xc</guid>
    </item>
  </channel>
</rss>
