<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-15T15:12:55.473260+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cve-2026-18408</id>
    <title>CVE-2026-18408 — PostgreSQL psql \unrestrict lets superuser of pg_dump origin server execute arbitrary code in psql client</title>
    <updated>2026-10-15T15:12:55.475854+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PostgreSQL</p>
<p>Untrusted data inclusion in pg_dump in PostgreSQL allows a malicious superuser of the origin server to inject arbitrary code for restore-time execution as the client operating system account running psql to restore the dump, via psql \restrict meta-command input expansion.  The fix for CVE-2025-8714 introduced \restrict and \unrestrict to block this attack, but \unrestrict itself was sufficient for an attack.  pg_dumpall is also affected.  pg_restore is affected when used to generate a plain-format dump.  Non-core use of \restrict would be affected, but we've not identified non-core use.  Versions before PostgreSQL 18.6, 17.11, 16.15, 15.19, and 14.24 are affected.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cve-2026-18408"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/usn-8653-1</id>
    <title>USN-8653-1 — postgresql-14, postgresql-16, postgresql-18 vulnerabilities</title>
    <updated>2026-10-15T15:12:55.475929+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Ubuntu:22.04:LTS: postgresql-14, Ubuntu:24.04:LTS: postgresql-16, Ubuntu:26.04:LTS: postgresql-18</p>
<p>It was discovered that PostgreSQL incorrectly handled COPY FROM STDIN when
an early failure occurred. An authenticated user could possibly use this
issue to execute arbitrary SQL commands. (CVE-2026-6464)</p>
<p>It was discovered that PostgreSQL incorrectly reset extended statistics
ownership during ALTER TABLE ALTER TYPE operations. An attacker could
possibly use this issue to obtain sensitive information or gain unintended
privileges. (CVE-2026-6469)</p>
<p>It was discovered that PostgreSQL failed to check the USAGE privilege on
types. An authenticated user could possibly use this issue to obtain
sensitive information. (CVE-2026-6470)</p>
<p>It was discovered that PostgreSQL logical decoding could load arbitrary
shared libraries. An authenticated user could possibly use this issue to
execute arbitrary code. (CVE-2026-6471)</p>
<p>It was discovered that PostgreSQL had integer wraparound issues in tsvector
and tsquery allocations. An authenticated user could possibly use this
issue to execute arbitrary code. (CVE-2026-14662)</p>
<p>It was discovered that PostgreSQL pgcrypto silently used cleartext when
OpenSSL-disabled ciphers were requested. An authenticated user could
possibly use this issue to obtain sensitive information. (CVE-2026-14663)</p>
<p>It was discovered that PostgreSQL had a heap buffer overflow in regular
expression processing. An authenticated user could possibly use this issue
to execute arbitrary code. (CVE-2026-14664)</p>
<p>It was discovered that PostgreSQL row security policies were not properly…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/usn-8653-1"/>
  </entry>
</feed>
