<?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:56 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-398479</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-398479</link>
      <description>EUVD-2026-398479</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-398479</guid>
    </item>
    <item>
      <title>fkie_cve-2026-116246</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-116246</link>
      <description>&lt;p&gt;To pass a server&amp;#39;s password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin&amp;#39;s own process environment: as PGPASSWORD for the PSQL tool, and under a per-process variable for a utility. Nothing removed it afterwards. pgAdmin&amp;#39;s environment is shared by every user&amp;#39;s requests and copied into every process it starts, so in server mode another user&amp;#39;s later PSQL session or utility inherited the password, and libpq used PGPASSWORD for any connection made without a password of its own, letting one user connect with another user&amp;#39;s saved password.&lt;/p&gt;
&lt;p&gt;The fix puts the password only into the environment built for the process that needs it and starts psql with a copy of pgAdmin&amp;#39;s environment instead of the environment itself.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;To pass a server&amp;#39;s password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin&amp;#39;s own process environment: as PGPASSWORD for the PSQL tool, and under a per-process variable for a utility. Nothing removed it afterwards. pgAdmin&amp;#39;s environment is shared by every user&amp;#39;s requests and copied into every process it starts, so in server mode another user&amp;#39;s later PSQL session or utility inherited the password, and libpq used PGPASSWORD for any connection made without a password of its own, letting one user connect with another user&amp;#39;s saved password.&lt;/p&gt;
&lt;p&gt;The fix puts the password only into the environment built for the process that needs it and starts psql with a copy of pgAdmin&amp;#39;s environment instead of the environment itself.&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-116246</guid>
    </item>
    <item>
      <title>GHSA-835v-3mj2-2w29</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-835v-3mj2-2w29</link>
      <description>&lt;p&gt;To pass a server&amp;#39;s password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin&amp;#39;s own process environment: as PGPASSWORD for the PSQL tool, and under a per-process variable for a utility. Nothing removed it afterwards. pgAdmin&amp;#39;s environment is shared by every user&amp;#39;s requests and copied into every process it starts, so in server mode another user&amp;#39;s later PSQL session or utility inherited the password, and libpq used PGPASSWORD for any connection made without a password of its own, letting one user connect with another user&amp;#39;s saved password.&lt;/p&gt;
&lt;p&gt;The fix puts the password only into the environment built for the process that needs it and starts psql with a copy of pgAdmin&amp;#39;s environment instead of the environment itself.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;To pass a server&amp;#39;s password to psql and to the utilities pgAdmin 4 runs as background processes, the server manager wrote it into pgAdmin&amp;#39;s own process environment: as PGPASSWORD for the PSQL tool, and under a per-process variable for a utility. Nothing removed it afterwards. pgAdmin&amp;#39;s environment is shared by every user&amp;#39;s requests and copied into every process it starts, so in server mode another user&amp;#39;s later PSQL session or utility inherited the password, and libpq used PGPASSWORD for any connection made without a password of its own, letting one user connect with another user&amp;#39;s saved password.&lt;/p&gt;
&lt;p&gt;The fix puts the password only into the environment built for the process that needs it and starts psql with a copy of pgAdmin&amp;#39;s environment instead of the environment itself.&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-835v-3mj2-2w29</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>
