<?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>Fri, 02 Oct 2026 23:51:45 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-9545</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-9545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: curl, Alpaquita:25: curl, Alpaquita:stream: curl, BellSoft Hardened Containers:stream: curl&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Alpaquita:23: curl, Alpaquita:25: curl, Alpaquita:stream: curl, BellSoft Hardened Containers:stream: curl&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2026-9545</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0797 — De multiples vulnérabilités ont été découvertes dans cURL et libcurl. Certaines d'entre elles permettent à un attaquant…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0797</link>
      <description>certfr-2026-avi-0797</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0797</guid>
    </item>
    <item>
      <title>EUVD-2026-368435</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-368435</link>
      <description>EUVD-2026-368435</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-368435</guid>
    </item>
    <item>
      <title>fkie_cve-2026-9545</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-9545</link>
      <description>&lt;p&gt;In this scenario, libcurl first uses a proper HTTP/3 server for the initial
transfers, and when it makes a second transfer to the same site it has been
replaced by the attacker&amp;#39;s impostor machine - without a valid certificate.&lt;/p&gt;
&lt;p&gt;When libcurl returns to the hostname the second time with a cached SSL session
(`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the
`CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might
send off the second request&amp;#39;s bytes on that new connection *before* enforcing
the certificate verification failure. Potentially leaking sensitive
information.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In this scenario, libcurl first uses a proper HTTP/3 server for the initial
transfers, and when it makes a second transfer to the same site it has been
replaced by the attacker&amp;#39;s impostor machine - without a valid certificate.&lt;/p&gt;
&lt;p&gt;When libcurl returns to the hostname the second time with a cached SSL session
(`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the
`CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might
send off the second request&amp;#39;s bytes on that new connection *before* enforcing
the certificate verification failure. Potentially leaking sensitive
information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-9545</guid>
    </item>
    <item>
      <title>GHSA-6v72-wfcj-jv53</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6v72-wfcj-jv53</link>
      <description>&lt;p&gt;In this scenario, libcurl first uses a proper HTTP/3 server for the initial
transfers, and when it makes a second transfer to the same site it has been
replaced by the attacker&amp;#39;s impostor machine - without a valid certificate.&lt;/p&gt;
&lt;p&gt;When libcurl returns to the hostname the second time with a cached SSL session
(`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the
`CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might
send off the second request&amp;#39;s bytes on that new connection *before* enforcing
the certificate verification failure. Potentially leaking sensitive
information.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In this scenario, libcurl first uses a proper HTTP/3 server for the initial
transfers, and when it makes a second transfer to the same site it has been
replaced by the attacker&amp;#39;s impostor machine - without a valid certificate.&lt;/p&gt;
&lt;p&gt;When libcurl returns to the hostname the second time with a cached SSL session
(`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the
`CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might
send off the second request&amp;#39;s bytes on that new connection *before* enforcing
the certificate verification failure. Potentially leaking sensitive
information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6v72-wfcj-jv53</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-9545 — exposing HTTP/3 early data</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-9545</link>
      <description>msrc_CVE-2026-9545</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-9545</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11230-1 — curl-8.21.0-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:11230-1</link>
      <description>&lt;p&gt;curl-8.21.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;curl-8.21.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:11230-1</guid>
    </item>
    <item>
      <title>RHSA-2026:41240 — Red Hat Security Advisory: Red Hat Hardened Images RPMs Security Update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:41240</link>
      <description>&lt;p&gt;libcurl: libcurl: Information disclosure via cached SSL session and early data libcurl: libcurl: Use-after-free vulnerability leading to Denial of Service nghttp2: nghttp2: HTTP Request/Response Smuggling and Response-Queue Poisoning via ambiguous HTTP/1.1 Upgrade requests&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libcurl: libcurl: Information disclosure via cached SSL session and early data libcurl: libcurl: Use-after-free vulnerability leading to Denial of Service nghttp2: nghttp2: HTTP Request/Response Smuggling and Response-Queue Poisoning via ambiguous HTTP/1.1 Upgrade requests&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:41240</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:22553-1 — Security update for curl</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:22553-1</link>
      <description>&lt;p&gt;Security update for curl&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Security update for curl&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/suse-su-2026:22553-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-9545</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-9545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: curl, Ubuntu:26.04:LTS: curl&lt;/p&gt;
&lt;p&gt;In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker&amp;#39;s impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request&amp;#39;s bytes on that new connection *before* enforcing the certificate verification failure. Potentially leaking sensitive information.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:25.10: curl, Ubuntu:26.04:LTS: curl&lt;/p&gt;
&lt;p&gt;In this scenario, libcurl first uses a proper HTTP/3 server for the initial transfers, and when it makes a second transfer to the same site it has been replaced by the attacker&amp;#39;s impostor machine - without a valid certificate. When libcurl returns to the hostname the second time with a cached SSL session (`CURLOPT_SSL_SESSIONID_CACHE` is not disabled) and early data enabled (the `CURLSSLOPT_EARLYDATA` bit is set in `CURLOPT_SSL_OPTIONS`), libcurl might send off the second request&amp;#39;s bytes on that new connection *before* enforcing the certificate verification failure. Potentially leaking sensitive information.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-9545</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-2052 — cURL: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2052</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in cURL ausnutzen, um Sicherheitsvorkehrungen zu umgehen, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand oder eine Speicherbeschädigung zu verursachen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in cURL ausnutzen, um Sicherheitsvorkehrungen zu umgehen, vertrauliche Informationen offenzulegen oder einen Denial-of-Service-Zustand oder eine Speicherbeschädigung zu verursachen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-2052</guid>
    </item>
  </channel>
</rss>
