<?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-14T20:13:36.856241+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-14668</id>
    <title>CVE-2026-14668 — PostgreSQL ctid type confusion in selectivity estimator discloses derivative of arbitrary read</title>
    <updated>2026-10-14T20:13:36.876230+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> PostgreSQL</p>
<p>Type confusion regarding input of PostgreSQL ctid data type selectivity estimator allows an object creator to view a calculation derived from the value of an arbitrary 4-byte span of memory, via a chosen non-ctid input.  While the calculation loses precision, substantial memory value recovery appears possible.  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-14668"/>
  </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-14T20:13:36.876348+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>
