<?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 15:06:11 +0000</lastBuildDate>
    <item>
      <title>bdu:2026-09771</title>
      <link>https://cve.radiocsirt.org/vuln/bdu:2026-09771</link>
      <description>bdu:2026-09771</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bdu:2026-09771</guid>
    </item>
    <item>
      <title>BELL-CVE-2026-5545</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2026-5545</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-5545</guid>
    </item>
    <item>
      <title>certfr-2026-avi-0514 — De multiples vulnérabilités ont été découvertes dans Curl. Elles permettent à un attaquant de provoquer une atteinte à…</title>
      <link>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0514</link>
      <description>certfr-2026-avi-0514</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2026-avi-0514</guid>
    </item>
    <item>
      <title>EUVD-2026-368414</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-368414</link>
      <description>EUVD-2026-368414</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-368414</guid>
    </item>
    <item>
      <title>fkie_cve-2026-5545</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-5545</link>
      <description>&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to
do an authenticated HTTP(S) request after a Negotiate-authenticated one, when
both use the same host.&lt;/p&gt;
&lt;p&gt;libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.&lt;/p&gt;
&lt;p&gt;When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a request that was issued by an application could
wrongfully reuse an existing connection to the same server that was
authenticated using different credentials.&lt;/p&gt;
&lt;p&gt;An application that first uses Negotiate authentication to a server with
`user1:password1` and then does another operation to the same server asking
for any authentication method but for `user2:password2` (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1&amp;#39;s and user2&amp;#39;s credentials when it is in fact
still using the connection authenticated for user1...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to
do an authenticated HTTP(S) request after a Negotiate-authenticated one, when
both use the same host.&lt;/p&gt;
&lt;p&gt;libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.&lt;/p&gt;
&lt;p&gt;When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a request that was issued by an application could
wrongfully reuse an existing connection to the same server that was
authenticated using different credentials.&lt;/p&gt;
&lt;p&gt;An application that first uses Negotiate authentication to a server with
`user1:password1` and then does another operation to the same server asking
for any authentication method but for `user2:password2` (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1&amp;#39;s and user2&amp;#39;s credentials when it is in fact
still using the connection authenticated for user1...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-5545</guid>
    </item>
    <item>
      <title>GHSA-6g7g-56fm-f8mp</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6g7g-56fm-f8mp</link>
      <description>&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to
do an authenticated HTTP(S) request after a Negotiate-authenticated one, when
both use the same host.&lt;/p&gt;
&lt;p&gt;libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.&lt;/p&gt;
&lt;p&gt;When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a request that was issued by an application could
wrongfully reuse an existing connection to the same server that was
authenticated using different credentials.&lt;/p&gt;
&lt;p&gt;An application that first uses Negotiate authentication to a server with
`user1:password1` and then does another operation to the same server asking
for any authentication method but for `user2:password2` (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1&amp;#39;s and user2&amp;#39;s credentials when it is in fact
still using the connection authenticated for user1...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to
do an authenticated HTTP(S) request after a Negotiate-authenticated one, when
both use the same host.&lt;/p&gt;
&lt;p&gt;libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.&lt;/p&gt;
&lt;p&gt;When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a request that was issued by an application could
wrongfully reuse an existing connection to the same server that was
authenticated using different credentials.&lt;/p&gt;
&lt;p&gt;An application that first uses Negotiate authentication to a server with
`user1:password1` and then does another operation to the same server asking
for any authentication method but for `user2:password2` (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1&amp;#39;s and user2&amp;#39;s credentials when it is in fact
still using the connection authenticated for user1...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6g7g-56fm-f8mp</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-5545 — wrong reuse of HTTP Negotiate connection</title>
      <link>https://cve.radiocsirt.org/vuln/msrc_cve-2026-5545</link>
      <description>msrc_CVE-2026-5545</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/msrc_cve-2026-5545</guid>
    </item>
    <item>
      <title>OESA-2026-2451 — curl security update</title>
      <link>https://cve.radiocsirt.org/vuln/oesa-2026-2451</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: curl&lt;/p&gt;
&lt;p&gt;cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A vulnerability exists where a connection requiring TLS incorrectly reuses an
existing unencrypted connection from the same connection pool. If an initial
transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request
to that same host bypasses the TLS requirement and instead transmit data
unencrypted.(CVE-2026-4873)&lt;/p&gt;
&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to
do an authenticated HTTP(S) request after a Negotiate-authenticated one, when
both use the same host.&lt;/p&gt;
&lt;p&gt;libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.&lt;/p&gt;
&lt;p&gt;When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a request that was issued by an application could
wrongfully reuse an existing connection to the same server that was
authenticated using different credentials.&lt;/p&gt;
&lt;p&gt;An application that first uses Negotiate authentication to a server with
`user1:password1` and then does another operation to the same server asking
for any authentication method but for `user2:password2` (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1&amp;amp;apos;s and user2&amp;amp;apos;s creden…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:22.03-LTS-SP4: curl&lt;/p&gt;
&lt;p&gt;cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols.&#13;
&#13;
Security Fix(es):&lt;/p&gt;
&lt;p&gt;A vulnerability exists where a connection requiring TLS incorrectly reuses an
existing unencrypted connection from the same connection pool. If an initial
transfer is made in clear-text (via IMAP, SMTP, or POP3), a subsequent request
to that same host bypasses the TLS requirement and instead transmit data
unencrypted.(CVE-2026-4873)&lt;/p&gt;
&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to
do an authenticated HTTP(S) request after a Negotiate-authenticated one, when
both use the same host.&lt;/p&gt;
&lt;p&gt;libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.&lt;/p&gt;
&lt;p&gt;When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a request that was issued by an application could
wrongfully reuse an existing connection to the same server that was
authenticated using different credentials.&lt;/p&gt;
&lt;p&gt;An application that first uses Negotiate authentication to a server with
`user1:password1` and then does another operation to the same server asking
for any authentication method but for `user2:password2` (while the previous
connection is still alive) - the second request gets confused and wrongly
reuses the same connection and sends the new request over that connection
thinking it uses a mix of user1&amp;amp;apos;s and user2&amp;amp;apos;s creden…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/oesa-2026-2451</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:10674-1 — curl-8.20.0-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10674-1</link>
      <description>&lt;p&gt;curl-8.20.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;curl-8.20.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2026:10674-1</guid>
    </item>
    <item>
      <title>RHSA-2026:12916 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
      <link>https://cve.radiocsirt.org/vuln/rhsa-2026:12916</link>
      <description>&lt;p&gt;curl: curl: Information disclosure due to incorrect TLS connection reuse curl: libcurl: Authentication bypass due to incorrect HTTP Negotiate connection reuse curl: libcurl: Wrong file transfer due to incorrect SMB connection reuse curl: curl: Proxy credential disclosure via redirects to unauthenticated proxies curl: libcurl: Information disclosure due to cookie leak when reusing connections with custom Host headers curl: libcurl: Credential leak via reused proxy connection during HTTP redirects&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;curl: curl: Information disclosure due to incorrect TLS connection reuse curl: libcurl: Authentication bypass due to incorrect HTTP Negotiate connection reuse curl: libcurl: Wrong file transfer due to incorrect SMB connection reuse curl: curl: Proxy credential disclosure via redirects to unauthenticated proxies curl: libcurl: Information disclosure due to cookie leak when reusing connections with custom Host headers curl: libcurl: Credential leak via reused proxy connection during HTTP redirects&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/rhsa-2026:12916</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:1940-1 — Security update for curl</title>
      <link>https://cve.radiocsirt.org/vuln/suse-su-2026:1940-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:1940-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-5545</title>
      <link>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5545</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: curl, Ubuntu:22.04:LTS: curl, Ubuntu:24.04:LTS: curl, Ubuntu:25.10: curl, Ubuntu:26.04:LTS: curl&lt;/p&gt;
&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1&amp;#39;s and user2&amp;#39;s credentials when it is in fact still using the connection authenticated for user1...&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:20.04:LTS: curl, Ubuntu:22.04:LTS: curl, Ubuntu:24.04:LTS: curl, Ubuntu:25.10: curl, Ubuntu:26.04:LTS: curl&lt;/p&gt;
&lt;p&gt;libcurl might in some circumstances reuse the wrong connection when asked to do an authenticated HTTP(S) request after a Negotiate-authenticated one, when both use the same host. libcurl features a pool of recent connections so that subsequent requests can reuse an existing connection to avoid overhead. When reusing a connection a range of criteria must be met. Due to a logical error in the code, a request that was issued by an application could wrongfully reuse an existing connection to the same server that was authenticated using different credentials. An application that first uses Negotiate authentication to a server with `user1:password1` and then does another operation to the same server asking for any authentication method but for `user2:password2` (while the previous connection is still alive) - the second request gets confused and wrongly reuses the same connection and sends the new request over that connection thinking it uses a mix of user1&amp;#39;s and user2&amp;#39;s credentials when it is in fact still using the connection authenticated for user1...&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5545</guid>
    </item>
    <item>
      <title>WID-SEC-W-2026-1307 — cURL: Mehrere Schwachstellen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1307</link>
      <description>&lt;p&gt;Ein Angreifer kann mehrere Schwachstellen in cURL ausnutzen, um Sicherheitsvorkehrungen zu umgehen, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.&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 Daten zu manipulieren.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1307</guid>
    </item>
  </channel>
</rss>
