<?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://vulnerability.circl.lu</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>Mon, 28 Sep 2026 21:30:10 +0000</lastBuildDate>
    <item>
      <title>CVE-2026-9545 — exposing HTTP/3 early data</title>
      <link>https://vulnerability.circl.lu/vuln/cve-2026-9545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; 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.&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;&lt;strong&gt;Affected:&lt;/strong&gt; 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.&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://vulnerability.circl.lu/vuln/cve-2026-9545</guid>
    </item>
  </channel>
</rss>
