<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-02T20:35:43.976665+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bdu:2026-09772</id>
    <title>bdu:2026-09772</title>
    <updated>2026-10-02T20:35:44.060778+00:00</updated>
    <content>bdu:2026-09772</content>
    <link href="https://cve.radiocsirt.org/vuln/bdu:2026-09772"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/bell-cve-2026-5773</id>
    <title>BELL-CVE-2026-5773</title>
    <updated>2026-10-02T20:35:44.060818+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p><strong>Affected:</strong> Alpaquita:23: curl, Alpaquita:25: curl, Alpaquita:stream: curl, BellSoft Hardened Containers:stream: curl</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2026-5773"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2026-avi-0514</id>
    <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>
    <updated>2026-10-02T20:35:44.060851+00:00</updated>
    <content>certfr-2026-avi-0514</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2026-avi-0514"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-368415</id>
    <title>EUVD-2026-368415</title>
    <updated>2026-10-02T20:35:44.060869+00:00</updated>
    <content>EUVD-2026-368415</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-368415"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-5773</id>
    <title>fkie_cve-2026-5773</title>
    <updated>2026-10-02T20:35:44.060881+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>libcurl might in some circumstances reuse the wrong connection for SMB(S)
transfers.</p>
<p>libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.</p>
<p>When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a network transfer operation that was requested by an
application could wrongfully reuse an existing SMB connection to the same
server that was using a different "share" than the new subsequent transfer
should.</p>
<p>This could in unlucky situations lead to the download of the wrong file or the
upload of a file to the wrong place. When this happens, the same credentials
are used and the server name is the same.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-5773"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-rp9q-8q5w-ch44</id>
    <title>GHSA-rp9q-8q5w-ch44</title>
    <updated>2026-10-02T20:35:44.060911+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>libcurl might in some circumstances reuse the wrong connection for SMB(S)
transfers.</p>
<p>libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.</p>
<p>When reusing a connection a range of criteria must be met. Due to a logical
error in the code, a network transfer operation that was requested by an
application could wrongfully reuse an existing SMB connection to the same
server that was using a different 'share' than the new subsequent transfer
should.</p>
<p>This could in unlucky situations lead to the download of the wrong file or the
upload of a file to the wrong place. When this happens, the same credentials
are used and the server name is the same.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-rp9q-8q5w-ch44"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/msrc_cve-2026-5773</id>
    <title>msrc_CVE-2026-5773 — wrong reuse of SMB connection</title>
    <updated>2026-10-02T20:35:44.060931+00:00</updated>
    <content>msrc_CVE-2026-5773</content>
    <link href="https://cve.radiocsirt.org/vuln/msrc_cve-2026-5773"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/oesa-2026-2451</id>
    <title>OESA-2026-2451 — curl security update</title>
    <updated>2026-10-02T20:35:44.060947+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> openEuler:22.03-LTS-SP4: curl</p>
<p>cURL is a computer software project providing a library (libcurl) and command-line tool (curl) for transferring data using various protocols.

Security Fix(es):</p>
<p>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)</p>
<p>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.</p>
<p>libcurl features a pool of recent connections so that subsequent requests can
reuse an existing connection to avoid overhead.</p>
<p>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.</p>
<p>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;apos;s and user2&amp;apos;s creden…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/oesa-2026-2451"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2026:10674-1</id>
    <title>openSUSE-SU-2026:10674-1 — curl-8.20.0-1.1 on GA media</title>
    <updated>2026-10-02T20:35:44.060992+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>curl-8.20.0-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2026:10674-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/rhsa-2026:12916</id>
    <title>RHSA-2026:12916 — Red Hat Security Advisory: Red Hat Hardened Images RPMs bug fix and enhancement update</title>
    <updated>2026-10-02T20:35:44.061011+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>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</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/rhsa-2026:12916"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/suse-su-2026:23350-1</id>
    <title>SUSE-SU-2026:23350-1 — Security update for curl</title>
    <updated>2026-10-02T20:35:44.061035+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Security update for curl</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/suse-su-2026:23350-1"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5773</id>
    <title>UBUNTU-CVE-2026-5773</title>
    <updated>2026-10-02T20:35:44.061050+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> 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:25.10: curl, Ubuntu:26.04:LTS: curl</p>
<p>libcurl might in some circumstances reuse the wrong connection for SMB(S) transfers. 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 network transfer operation that was requested by an application could wrongfully reuse an existing SMB connection to the same server that was using a different "share" than the new subsequent transfer should. This could in unlucky situations lead to the download of the wrong file or the upload of a file to the wrong place. When this happens, the same credentials are used and the server name is the same.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ubuntu-cve-2026-5773"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/vde-2026-088</id>
    <title>VDE-2026-088 — METTLER TOLEDO: LabX Standard and Enterprise Report on External Component Analysis - v21.4</title>
    <updated>2026-10-02T20:35:44.061080+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p>The vulnerabilities found in LabX Standard versions 21.3.22 - 21.4.23 are CVE-2025-69419, CVE-2026-0915, CVE-2025-15467, CVE-2026-4800, CVE-2026-33186, CVE-2026-39821, CVE-2026-33671 and are fixed in LabX Standard v21.4.25.</p>
<p>The vulnerabilities found in LabX Enterprise versions 21.3.22 - 21.4.23 are CVE-2026-4800, CVE-2026-33186, CVE-2026-39821, CVE-2026-33671 and are fixed in LabX Enterprise v21.4.25</p>
<p>All other vulnerabilities are to be fixed in the upcoming releases.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/vde-2026-088"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1307</id>
    <title>WID-SEC-W-2026-1307 — cURL: Mehrere Schwachstellen</title>
    <updated>2026-10-02T20:35:44.061120+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Ein Angreifer kann mehrere Schwachstellen in cURL ausnutzen, um Sicherheitsvorkehrungen zu umgehen, vertrauliche Informationen offenzulegen oder Daten zu manipulieren.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/wid-sec-w-2026-1307"/>
  </entry>
</feed>
