<?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>Sat, 03 Oct 2026 03:40:44 +0000</lastBuildDate>
    <item>
      <title>bdu:2024-01984</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2024-01984</link>
      <description>bdu:2024-01984</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2024-01984</guid>
    </item>
    <item>
      <title>EUVD-2026-9572</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-9572</link>
      <description>EUVD-2026-9572</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-9572</guid>
    </item>
    <item>
      <title>fkie_cve-2024-2339</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2024-2339</link>
      <description>&lt;p&gt;PostgreSQL Anonymizer v1.2 contains a vulnerability  that allows a user who owns a table to elevate to superuser. A user can define a masking function for a column and place malicious code in that function. When a privileged user applies the masking rules using the static masking or the anonymous dump method, the malicious code is executed and can grant escalated privileges to the malicious user. PostgreSQL Anonymizer v1.2 does provide a protection against this risk with the restrict_to_trusted_schemas option, but that protection is incomplete. Users that don&amp;#39;t own a table, especially masked users cannot exploit this vulnerability. The problem is resolved in v1.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PostgreSQL Anonymizer v1.2 contains a vulnerability  that allows a user who owns a table to elevate to superuser. A user can define a masking function for a column and place malicious code in that function. When a privileged user applies the masking rules using the static masking or the anonymous dump method, the malicious code is executed and can grant escalated privileges to the malicious user. PostgreSQL Anonymizer v1.2 does provide a protection against this risk with the restrict_to_trusted_schemas option, but that protection is incomplete. Users that don&amp;#39;t own a table, especially masked users cannot exploit this vulnerability. The problem is resolved in v1.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2024-2339</guid>
    </item>
    <item>
      <title>GHSA-fvc5-hrmq-8hx4</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fvc5-hrmq-8hx4</link>
      <description>&lt;p&gt;PostgreSQL Anonymizer v1.2 contains a vulnerability  that allows a user who owns a table to elevate to superuser. A user can define a masking function for a column and place malicious code in that function. When a privileged user applies the masking rules using the static masking or the anonymous dump method, the malicious code is executed and can grant escalated privileges to the malicious user. PostgreSQL Anonymizer v1.2 does provide a protection against this risk with the restrict_to_trusted_schemas option, but that protection is incomplete. Users that don&amp;#39;t own a table, especially masked users cannot exploit this vulnerability. The problem is resolved in v1.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PostgreSQL Anonymizer v1.2 contains a vulnerability  that allows a user who owns a table to elevate to superuser. A user can define a masking function for a column and place malicious code in that function. When a privileged user applies the masking rules using the static masking or the anonymous dump method, the malicious code is executed and can grant escalated privileges to the malicious user. PostgreSQL Anonymizer v1.2 does provide a protection against this risk with the restrict_to_trusted_schemas option, but that protection is incomplete. Users that don&amp;#39;t own a table, especially masked users cannot exploit this vulnerability. The problem is resolved in v1.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fvc5-hrmq-8hx4</guid>
    </item>
    <item>
      <title>gsd-2024-2339</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2024-2339</link>
      <description>gsd-2024-2339</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2024-2339</guid>
    </item>
  </channel>
</rss>
