<?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 19:15:58 +0000</lastBuildDate>
    <item>
      <title>BELL-CVE-2026-80230</title>
      <link>https://vulnerability.circl.lu/vuln/bell-cve-2026-80230</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://vulnerability.circl.lu/vuln/bell-cve-2026-80230</guid>
    </item>
    <item>
      <title>certfr-2026-avi-1108 — De multiples vulnérabilités ont été découvertes dans Curl. Certaines d'entre elles permettent à un attaquant de provoqu…</title>
      <link>https://vulnerability.circl.lu/vuln/certfr-2026-avi-1108</link>
      <description>certfr-2026-avi-1108</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/certfr-2026-avi-1108</guid>
    </item>
    <item>
      <title>fkie_cve-2026-80230</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-80230</link>
      <description>&lt;p&gt;When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable
standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and
`CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on
connections established without a presented server certificate. Bypassing the
pinning check under these disabled-verification conditions allows
unauthenticated connections to succeed when they should be rejected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable
standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and
`CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on
connections established without a presented server certificate. Bypassing the
pinning check under these disabled-verification conditions allows
unauthenticated connections to succeed when they should be rejected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-80230</guid>
    </item>
    <item>
      <title>GHSA-2xgv-7q8p-67gc</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-2xgv-7q8p-67gc</link>
      <description>&lt;p&gt;When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable
standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and
`CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on
connections established without a presented server certificate. Bypassing the
pinning check under these disabled-verification conditions allows
unauthenticated connections to succeed when they should be rejected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable
standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and
`CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on
connections established without a presented server certificate. Bypassing the
pinning check under these disabled-verification conditions allows
unauthenticated connections to succeed when they should be rejected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-2xgv-7q8p-67gc</guid>
    </item>
    <item>
      <title>msrc_CVE-2026-80230 — OpenSSL pinning bypass</title>
      <link>https://vulnerability.circl.lu/vuln/msrc_cve-2026-80230</link>
      <description>msrc_CVE-2026-80230</description>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/msrc_cve-2026-80230</guid>
    </item>
    <item>
      <title>OESA-2026-4124 — curl security update</title>
      <link>https://vulnerability.circl.lu/vuln/oesa-2026-4124</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;Successfully using libcurl to do a transfer to a specific HTTP origin
(`hostA`) with **Digest** authentication and then changing the origin to a
different one (`hostB`) for a second transfer, reusing the same handle, makes
libcurl wrongly pass on the `Authorization:` header field meant for `hostA`,
to `hostB`.(CVE-2026-11856)&lt;/p&gt;
&lt;p&gt;A flaw in libcurl&amp;amp;apos;s handling of HTTP/2 Server Push streams, when the parent
handle is set to share connections with other handles, can lead to
use-after-free in the cleanup process.(CVE-2026-18924)&lt;/p&gt;
&lt;p&gt;A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given
hostname using Negotiate authentication, when the initial request is done
using empty credentials. This can make user B&amp;amp;apos;s request get sent over user A&amp;amp;apos;s
previously authenticated connection.(CVE-2026-19931)&lt;/p&gt;
&lt;p&gt;When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable
standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and
`CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on
connections established without a presented server certificate. Bypassing the
pinning check under these disabled-verification conditions allows
unauthenticated connections to succeed when they should be rejected.(CVE-2026-80230)&lt;/p&gt;
&lt;p&gt;A flaw in libcurl makes it wrongly reuse an existing HTTPS con…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; openEuler:20.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;Successfully using libcurl to do a transfer to a specific HTTP origin
(`hostA`) with **Digest** authentication and then changing the origin to a
different one (`hostB`) for a second transfer, reusing the same handle, makes
libcurl wrongly pass on the `Authorization:` header field meant for `hostA`,
to `hostB`.(CVE-2026-11856)&lt;/p&gt;
&lt;p&gt;A flaw in libcurl&amp;amp;apos;s handling of HTTP/2 Server Push streams, when the parent
handle is set to share connections with other handles, can lead to
use-after-free in the cleanup process.(CVE-2026-18924)&lt;/p&gt;
&lt;p&gt;A flaw in libcurl makes it wrongly reuse an HTTP connection setup for a given
hostname using Negotiate authentication, when the initial request is done
using empty credentials. This can make user B&amp;amp;apos;s request get sent over user A&amp;amp;apos;s
previously authenticated connection.(CVE-2026-19931)&lt;/p&gt;
&lt;p&gt;When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable
standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and
`CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on
connections established without a presented server certificate. Bypassing the
pinning check under these disabled-verification conditions allows
unauthenticated connections to succeed when they should be rejected.(CVE-2026-80230)&lt;/p&gt;
&lt;p&gt;A flaw in libcurl makes it wrongly reuse an existing HTTPS con…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/oesa-2026-4124</guid>
    </item>
    <item>
      <title>openSUSE-SU-2026:11696-1 — curl-8.22.0-1.1 on GA media</title>
      <link>https://vulnerability.circl.lu/vuln/opensuse-su-2026:11696-1</link>
      <description>&lt;p&gt;curl-8.22.0-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;curl-8.22.0-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/opensuse-su-2026:11696-1</guid>
    </item>
    <item>
      <title>RHSA-2026:63161 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
      <link>https://vulnerability.circl.lu/vuln/rhsa-2026:63161</link>
      <description>&lt;p&gt;curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication curl: curl: Public key pinning bypass allows unauthenticated connections curl: curl: Incorrect HTTPS connection reuse with Native CA Store curl: curl: Information disclosure due to secure cookie attribute bypass curl: libcurl: Information disclosure via improper Public Suffix List boundary check&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;curl: curl: Authentication bypass in OpenLDAP SASL negotiation via Man-in-the-Middle (MITM) attack curl: libcurl: Use-after-free in HTTP/2 Server Push with shared connections curl: libcurl: Information disclosure via incorrect connection reuse with Negotiate authentication curl: curl: Public key pinning bypass allows unauthenticated connections curl: curl: Incorrect HTTPS connection reuse with Native CA Store curl: curl: Information disclosure due to secure cookie attribute bypass curl: libcurl: Information disclosure via improper Public Suffix List boundary check&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/rhsa-2026:63161</guid>
    </item>
    <item>
      <title>SUSE-SU-2026:23498-1 — Security update for curl</title>
      <link>https://vulnerability.circl.lu/vuln/suse-su-2026:23498-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://vulnerability.circl.lu/vuln/suse-su-2026:23498-1</guid>
    </item>
    <item>
      <title>UBUNTU-CVE-2026-80230</title>
      <link>https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-80230</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: curl, Ubuntu:Pro:18.04:LTS: curl, Ubuntu:Pro:20.04:LTS: curl, Ubuntu:22.04:LTS: curl, Ubuntu:24.04:LTS: curl, Ubuntu:26.04:LTS: curl&lt;/p&gt;
&lt;p&gt;When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Ubuntu:Pro:16.04:LTS: curl, Ubuntu:Pro:18.04:LTS: curl, Ubuntu:Pro:20.04:LTS: curl, Ubuntu:22.04:LTS: curl, Ubuntu:24.04:LTS: curl, Ubuntu:26.04:LTS: curl&lt;/p&gt;
&lt;p&gt;When `CURLOPT_PINNEDPUBLICKEY` is configured alongside options that disable standard peer verification (`CURLOPT_SSL_VERIFYPEER = 0` and `CURLOPT_SSL_VERIFYHOST = 0`), libcurl fails to enforce public key pinning on connections established without a presented server certificate. Bypassing the pinning check under these disabled-verification conditions allows unauthenticated connections to succeed when they should be rejected.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ubuntu-cve-2026-80230</guid>
    </item>
  </channel>
</rss>
