<?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://cve.radiocsirt.org</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>Mon, 16 Nov 2026 20:02:26 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-398482</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-398482</link>
      <description>EUVD-2026-398482</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-398482</guid>
    </item>
    <item>
      <title>fkie_cve-2026-116249</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-116249</link>
      <description>&lt;p&gt;In server mode pgAdmin 4 resolves a server&amp;#39;s password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user&amp;#39;s storage directory, but get_complete_file_path() only stripped leading slashes before joining the two. A path such as &amp;#34;../&amp;lt;another user&amp;gt;/.pgpass&amp;#34;, set through the server dialog, the REST API or a servers.json import, therefore named another user&amp;#39;s file, and connecting used that user&amp;#39;s saved passwords, client certificate or SSH key. The sslkeylogfile connection parameter was passed to libpq unchanged, so a path outside storage let libpq create or append a file as the account running pgAdmin.&lt;/p&gt;
&lt;p&gt;make_conninfo() also quoted connection parameter values but not their names, so a crafted parameter name could smuggle additional keyword=value pairs past these checks.&lt;/p&gt;
&lt;p&gt;The fix requires the resolved path, with symbolic links followed, to stay inside the user&amp;#39;s storage directory or the named shared storage directory, confines sslkeylogfile the same way, and accepts only exact libpq keywords as connection parameter names. A refused path or keyword is reported instead of letting libpq fall back to a default.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In server mode pgAdmin 4 resolves a server&amp;#39;s password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user&amp;#39;s storage directory, but get_complete_file_path() only stripped leading slashes before joining the two. A path such as &amp;#34;../&amp;lt;another user&amp;gt;/.pgpass&amp;#34;, set through the server dialog, the REST API or a servers.json import, therefore named another user&amp;#39;s file, and connecting used that user&amp;#39;s saved passwords, client certificate or SSH key. The sslkeylogfile connection parameter was passed to libpq unchanged, so a path outside storage let libpq create or append a file as the account running pgAdmin.&lt;/p&gt;
&lt;p&gt;make_conninfo() also quoted connection parameter values but not their names, so a crafted parameter name could smuggle additional keyword=value pairs past these checks.&lt;/p&gt;
&lt;p&gt;The fix requires the resolved path, with symbolic links followed, to stay inside the user&amp;#39;s storage directory or the named shared storage directory, confines sslkeylogfile the same way, and accepts only exact libpq keywords as connection parameter names. A refused path or keyword is reported instead of letting libpq fall back to a default.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-116249</guid>
    </item>
    <item>
      <title>GHSA-hw9h-5hmm-63g6</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-hw9h-5hmm-63g6</link>
      <description>&lt;p&gt;In server mode pgAdmin 4 resolves a server&amp;#39;s password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user&amp;#39;s storage directory, but get_complete_file_path() only stripped leading slashes before joining the two. A path such as &amp;#34;../&amp;lt;another user&amp;gt;/.pgpass&amp;#34;, set through the server dialog, the REST API or a servers.json import, therefore named another user&amp;#39;s file, and connecting used that user&amp;#39;s saved passwords, client certificate or SSH key. The sslkeylogfile connection parameter was passed to libpq unchanged, so a path outside storage let libpq create or append a file as the account running pgAdmin.&lt;/p&gt;
&lt;p&gt;make_conninfo() also quoted connection parameter values but not their names, so a crafted parameter name could smuggle additional keyword=value pairs past these checks.&lt;/p&gt;
&lt;p&gt;The fix requires the resolved path, with symbolic links followed, to stay inside the user&amp;#39;s storage directory or the named shared storage directory, confines sslkeylogfile the same way, and accepts only exact libpq keywords as connection parameter names. A refused path or keyword is reported instead of letting libpq fall back to a default.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In server mode pgAdmin 4 resolves a server&amp;#39;s password file, SSL certificate, key, CRL and SSH tunnel identity file relative to the user&amp;#39;s storage directory, but get_complete_file_path() only stripped leading slashes before joining the two. A path such as &amp;#34;../&amp;lt;another user&amp;gt;/.pgpass&amp;#34;, set through the server dialog, the REST API or a servers.json import, therefore named another user&amp;#39;s file, and connecting used that user&amp;#39;s saved passwords, client certificate or SSH key. The sslkeylogfile connection parameter was passed to libpq unchanged, so a path outside storage let libpq create or append a file as the account running pgAdmin.&lt;/p&gt;
&lt;p&gt;make_conninfo() also quoted connection parameter values but not their names, so a crafted parameter name could smuggle additional keyword=value pairs past these checks.&lt;/p&gt;
&lt;p&gt;The fix requires the resolved path, with symbolic links followed, to stay inside the user&amp;#39;s storage directory or the named shared storage directory, confines sslkeylogfile the same way, and accepts only exact libpq keywords as connection parameter names. A refused path or keyword is reported instead of letting libpq fall back to a default.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-hw9h-5hmm-63g6</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-4242 — pgAdmin: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4242</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in pgAdmin ausnutzen, um erweiterte Berechtigungen, möglicherweise sogar Administratorrechte, zu erlangen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren und offenzulegen oder Denial-of-Service-Angriffe zu starten.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in pgAdmin ausnutzen, um erweiterte Berechtigungen, möglicherweise sogar Administratorrechte, zu erlangen, um beliebigen Code auszuführen, Sicherheitsmaßnahmen zu umgehen, Daten zu manipulieren und offenzulegen oder Denial-of-Service-Angriffe zu starten.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-4242</guid>
    </item>
  </channel>
</rss>
