<?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>Sun, 04 Oct 2026 05:29:47 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-212280</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-212280</link>
      <description>EUVD-2026-212280</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-212280</guid>
    </item>
    <item>
      <title>fkie_cve-2023-31136</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-31136</link>
      <description>&lt;p&gt;PostgresNIO is a Swift client for PostgreSQL. Any user of PostgresNIO prior to version 1.14.2 connecting to servers with TLS enabled is vulnerable to a man-in-the-middle attacker injecting false responses to the client&amp;#39;s first few queries, despite the use of TLS certificate verification and encryption. The vulnerability is addressed in PostgresNIO versions starting from 1.14.2. There are no known workarounds for unpatched users.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;PostgresNIO is a Swift client for PostgreSQL. Any user of PostgresNIO prior to version 1.14.2 connecting to servers with TLS enabled is vulnerable to a man-in-the-middle attacker injecting false responses to the client&amp;#39;s first few queries, despite the use of TLS certificate verification and encryption. The vulnerability is addressed in PostgresNIO versions starting from 1.14.2. There are no known workarounds for unpatched users.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-31136</guid>
    </item>
    <item>
      <title>GHSA-9cfh-vx93-84vv — PostgresNIO processes unencrypted bytes from man-in-the-middle</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-9cfh-vx93-84vv</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; SwiftURL: github.com/vapor/postgres-nio&lt;/p&gt;
&lt;p&gt;### Impact
Any user of PostgresNIO connecting to servers with TLS enabled is vulnerable to a man-in-the-middle attacker injecting false responses to the client&amp;#39;s first few queries, despite the use of TLS certificate verification and encryption.&lt;/p&gt;
&lt;p&gt;_The remaining text in this section is quoted verbatim from [PostgreSQL&amp;#39;s CVE-2021-23222 advisory](https://www.postgresql.org/support/security/CVE-2021-23222/):_&lt;/p&gt;
&lt;p&gt;&amp;gt; If more preconditions hold, the attacker can exfiltrate the client&amp;#39;s password or other confidential data that might be transmitted early in a session. The attacker must have a way to trick the client&amp;#39;s intended server into making the confidential data accessible to the attacker. A known implementation having that property is a PostgreSQL configuration vulnerable to [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/). As with any exploitation of [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/), the server must be using trust authentication with a clientcert requirement or using cert authentication. To disclose a password, the client must be in possession of a password, which is atypical when using an authentication configuration vulnerable to [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/). The attacker must have some other way to access the server to retrieve the exfiltrated data (a valid, unprivileged login account would be sufficient).&lt;/p&gt;
&lt;p&gt;### Patches
The vulnerability is addressed in Post…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; SwiftURL: github.com/vapor/postgres-nio&lt;/p&gt;
&lt;p&gt;### Impact
Any user of PostgresNIO connecting to servers with TLS enabled is vulnerable to a man-in-the-middle attacker injecting false responses to the client&amp;#39;s first few queries, despite the use of TLS certificate verification and encryption.&lt;/p&gt;
&lt;p&gt;_The remaining text in this section is quoted verbatim from [PostgreSQL&amp;#39;s CVE-2021-23222 advisory](https://www.postgresql.org/support/security/CVE-2021-23222/):_&lt;/p&gt;
&lt;p&gt;&amp;gt; If more preconditions hold, the attacker can exfiltrate the client&amp;#39;s password or other confidential data that might be transmitted early in a session. The attacker must have a way to trick the client&amp;#39;s intended server into making the confidential data accessible to the attacker. A known implementation having that property is a PostgreSQL configuration vulnerable to [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/). As with any exploitation of [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/), the server must be using trust authentication with a clientcert requirement or using cert authentication. To disclose a password, the client must be in possession of a password, which is atypical when using an authentication configuration vulnerable to [CVE-2021-23214](https://www.postgresql.org/support/security/CVE-2021-23214/). The attacker must have some other way to access the server to retrieve the exfiltrated data (a valid, unprivileged login account would be sufficient).&lt;/p&gt;
&lt;p&gt;### Patches
The vulnerability is addressed in Post…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-9cfh-vx93-84vv</guid>
    </item>
    <item>
      <title>gsd-2023-31136</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-31136</link>
      <description>gsd-2023-31136</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-31136</guid>
    </item>
  </channel>
</rss>
