<?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-398474</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-398474</link>
      <description>EUVD-2026-398474</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-398474</guid>
    </item>
    <item>
      <title>fkie_cve-2026-116241</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-116241</link>
      <description>&lt;p&gt;pgAdmin 4&amp;#39;s Import/Export Data tool wraps a user&amp;#39;s query export in a psql \copy (...) TO command and checks that the query&amp;#39;s parentheses are balanced so that nothing can escape the wrapper. The check rejected a backslash inside a single-quoted string, but not inside a double-quoted identifier, where it treated the next double quote as closing the identifier. psql&amp;#39;s \copy parser applies the connection&amp;#39;s escape character to whichever quote opened a token, so with standard_conforming_strings off a backslash-escaped double quote does not close the identifier. pgAdmin&amp;#39;s and psql&amp;#39;s view of the quoting then diverged, a closing parenthesis hidden from the check ended the \copy (...) wrapper, and a following TO PROGRAM clause was executed by psql on the pgAdmin host, as the operating-system account running pgAdmin, before the server rejected the statement. An ordinary database role can turn standard_conforming_strings off for itself, and the Import/Export Data permission is granted to non-administrators by default.&lt;/p&gt;
&lt;p&gt;This is a bypass of the fix for CVE-2026-17566. The fix rejects any backslash inside a double-quoted identifier, as was already done for single-quoted strings, since its meaning depends on a server setting that cannot be known reliably when the query is validated.&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&amp;#39;s Import/Export Data tool wraps a user&amp;#39;s query export in a psql \copy (...) TO command and checks that the query&amp;#39;s parentheses are balanced so that nothing can escape the wrapper. The check rejected a backslash inside a single-quoted string, but not inside a double-quoted identifier, where it treated the next double quote as closing the identifier. psql&amp;#39;s \copy parser applies the connection&amp;#39;s escape character to whichever quote opened a token, so with standard_conforming_strings off a backslash-escaped double quote does not close the identifier. pgAdmin&amp;#39;s and psql&amp;#39;s view of the quoting then diverged, a closing parenthesis hidden from the check ended the \copy (...) wrapper, and a following TO PROGRAM clause was executed by psql on the pgAdmin host, as the operating-system account running pgAdmin, before the server rejected the statement. An ordinary database role can turn standard_conforming_strings off for itself, and the Import/Export Data permission is granted to non-administrators by default.&lt;/p&gt;
&lt;p&gt;This is a bypass of the fix for CVE-2026-17566. The fix rejects any backslash inside a double-quoted identifier, as was already done for single-quoted strings, since its meaning depends on a server setting that cannot be known reliably when the query is validated.&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-116241</guid>
    </item>
    <item>
      <title>GHSA-3jx6-4898-6q3m</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-3jx6-4898-6q3m</link>
      <description>&lt;p&gt;pgAdmin 4&amp;#39;s Import/Export Data tool wraps a user&amp;#39;s query export in a psql \copy (...) TO command and checks that the query&amp;#39;s parentheses are balanced so that nothing can escape the wrapper. The check rejected a backslash inside a single-quoted string, but not inside a double-quoted identifier, where it treated the next double quote as closing the identifier. psql&amp;#39;s \copy parser applies the connection&amp;#39;s escape character to whichever quote opened a token, so with standard_conforming_strings off a backslash-escaped double quote does not close the identifier. pgAdmin&amp;#39;s and psql&amp;#39;s view of the quoting then diverged, a closing parenthesis hidden from the check ended the \copy (...) wrapper, and a following TO PROGRAM clause was executed by psql on the pgAdmin host, as the operating-system account running pgAdmin, before the server rejected the statement. An ordinary database role can turn standard_conforming_strings off for itself, and the Import/Export Data permission is granted to non-administrators by default.&lt;/p&gt;
&lt;p&gt;This is a bypass of the fix for CVE-2026-17566. The fix rejects any backslash inside a double-quoted identifier, as was already done for single-quoted strings, since its meaning depends on a server setting that cannot be known reliably when the query is validated.&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&amp;#39;s Import/Export Data tool wraps a user&amp;#39;s query export in a psql \copy (...) TO command and checks that the query&amp;#39;s parentheses are balanced so that nothing can escape the wrapper. The check rejected a backslash inside a single-quoted string, but not inside a double-quoted identifier, where it treated the next double quote as closing the identifier. psql&amp;#39;s \copy parser applies the connection&amp;#39;s escape character to whichever quote opened a token, so with standard_conforming_strings off a backslash-escaped double quote does not close the identifier. pgAdmin&amp;#39;s and psql&amp;#39;s view of the quoting then diverged, a closing parenthesis hidden from the check ended the \copy (...) wrapper, and a following TO PROGRAM clause was executed by psql on the pgAdmin host, as the operating-system account running pgAdmin, before the server rejected the statement. An ordinary database role can turn standard_conforming_strings off for itself, and the Import/Export Data permission is granted to non-administrators by default.&lt;/p&gt;
&lt;p&gt;This is a bypass of the fix for CVE-2026-17566. The fix rejects any backslash inside a double-quoted identifier, as was already done for single-quoted strings, since its meaning depends on a server setting that cannot be known reliably when the query is validated.&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-3jx6-4898-6q3m</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>
