<?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>Tue, 17 Nov 2026 03:46:55 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-398478</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-398478</link>
      <description>EUVD-2026-398478</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-398478</guid>
    </item>
    <item>
      <title>fkie_cve-2026-116245</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-116245</link>
      <description>&lt;p&gt;libpq looks a connection service up in the service file of the operating-system account running pgAdmin 4, and an entry there can hold a password or name a password file or client certificate. In server mode any user could set a server&amp;#39;s Service, or a &amp;#34;service&amp;#34; connection parameter, to one of those entries and connect with its credentials. A PGPASSWORD or PGSERVICE variable set for that account was likewise used by libpq for every connection without a value of its own and passed on to the utilities, and pg_dumpall read a maintenance database name such as &amp;#34;service=...&amp;#34; as a connection string.&lt;/p&gt;
&lt;p&gt;The fix adds the SERVER_MODE_ALLOWED_SERVICES setting, empty by default: in server mode only a listed service can be used, the servicefile parameter is refused, and PGPASSWORD and PGSERVICE are removed from pgAdmin&amp;#39;s environment at startup. The allowlist is checked again on the final connection string, and the pg_dumpall database name is wrapped as a connection string.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libpq looks a connection service up in the service file of the operating-system account running pgAdmin 4, and an entry there can hold a password or name a password file or client certificate. In server mode any user could set a server&amp;#39;s Service, or a &amp;#34;service&amp;#34; connection parameter, to one of those entries and connect with its credentials. A PGPASSWORD or PGSERVICE variable set for that account was likewise used by libpq for every connection without a value of its own and passed on to the utilities, and pg_dumpall read a maintenance database name such as &amp;#34;service=...&amp;#34; as a connection string.&lt;/p&gt;
&lt;p&gt;The fix adds the SERVER_MODE_ALLOWED_SERVICES setting, empty by default: in server mode only a listed service can be used, the servicefile parameter is refused, and PGPASSWORD and PGSERVICE are removed from pgAdmin&amp;#39;s environment at startup. The allowlist is checked again on the final connection string, and the pg_dumpall database name is wrapped as a connection string.&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-116245</guid>
    </item>
    <item>
      <title>GHSA-mxqp-rrfg-8vgh</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-mxqp-rrfg-8vgh</link>
      <description>&lt;p&gt;libpq looks a connection service up in the service file of the operating-system account running pgAdmin 4, and an entry there can hold a password or name a password file or client certificate. In server mode any user could set a server&amp;#39;s Service, or a &amp;#34;service&amp;#34; connection parameter, to one of those entries and connect with its credentials. A PGPASSWORD or PGSERVICE variable set for that account was likewise used by libpq for every connection without a value of its own and passed on to the utilities, and pg_dumpall read a maintenance database name such as &amp;#34;service=...&amp;#34; as a connection string.&lt;/p&gt;
&lt;p&gt;The fix adds the SERVER_MODE_ALLOWED_SERVICES setting, empty by default: in server mode only a listed service can be used, the servicefile parameter is refused, and PGPASSWORD and PGSERVICE are removed from pgAdmin&amp;#39;s environment at startup. The allowlist is checked again on the final connection string, and the pg_dumpall database name is wrapped as a connection string.&lt;/p&gt;
&lt;p&gt;This issue affects pgAdmin 4: before 9.19.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libpq looks a connection service up in the service file of the operating-system account running pgAdmin 4, and an entry there can hold a password or name a password file or client certificate. In server mode any user could set a server&amp;#39;s Service, or a &amp;#34;service&amp;#34; connection parameter, to one of those entries and connect with its credentials. A PGPASSWORD or PGSERVICE variable set for that account was likewise used by libpq for every connection without a value of its own and passed on to the utilities, and pg_dumpall read a maintenance database name such as &amp;#34;service=...&amp;#34; as a connection string.&lt;/p&gt;
&lt;p&gt;The fix adds the SERVER_MODE_ALLOWED_SERVICES setting, empty by default: in server mode only a listed service can be used, the servicefile parameter is refused, and PGPASSWORD and PGSERVICE are removed from pgAdmin&amp;#39;s environment at startup. The allowlist is checked again on the final connection string, and the pg_dumpall database name is wrapped as a connection string.&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-mxqp-rrfg-8vgh</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>
