<?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-04T11:17:04.821557+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/bell-cve-2017-7468</id>
    <title>Withdrawn: BELL-CVE-2017-7468 — CVE-2017-7468 does not affect BellSoft software</title>
    <updated>2026-10-04T11:17:04.920886+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>
          <strong>Withdrawn by the publisher.</strong>
        </p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/bell-cve-2017-7468"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/certfr-2017-avi-229</id>
    <title>certfr-2017-avi-229 — De multiples vulnérabilités ont été corrigées dans &lt;span
class="textit"&gt;les produits Apple&lt;/span&gt;. Certaines d'entre el…</title>
    <updated>2026-10-04T11:17:04.920929+00:00</updated>
    <content>certfr-2017-avi-229</content>
    <link href="https://cve.radiocsirt.org/vuln/certfr-2017-avi-229"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cleanstart-2026-ay18527</id>
    <title>Withdrawn: CLEANSTART-2026-AY18527 — Security fixes for CVE-2014-0138, CVE-2014-0139, CVE-2016-5419, CVE-2016-5420, CVE-2016-5421, CVE-2016-7141, CVE-2016-7…</title>
    <updated>2026-10-04T11:17:04.920948+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Withdrawn by the publisher.</strong></p>
<p><strong>Affected:</strong> CleanStart: curl</p>
<p>Multiple security vulnerabilities affect the curl package. These issues are resolved in later releases. See references for individual vulnerability details.</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/cleanstart-2026-ay18527"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/cnvd-2017-06716</id>
    <title>cnvd-2017-06716</title>
    <updated>2026-10-04T11:17:04.920985+00:00</updated>
    <content>cnvd-2017-06716</content>
    <link href="https://cve.radiocsirt.org/vuln/cnvd-2017-06716"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-74720</id>
    <title>EUVD-2026-74720</title>
    <updated>2026-10-04T11:17:04.920998+00:00</updated>
    <content>EUVD-2026-74720</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-74720"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2017-7468</id>
    <title>fkie_cve-2017-7468</title>
    <updated>2026-10-04T11:17:04.921009+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was established by the previous certificate (or no certificate). libcurl supports by default the use of TLS session id/ticket to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason an existing TLS connection couldn't be kept alive to make the next handshake faster. This flaw is a regression and identical to CVE-2016-5419 reported on August 3rd 2016, but affecting a different version range.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2017-7468"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-5v44-xcm9-r9jw</id>
    <title>GHSA-5v44-xcm9-r9jw</title>
    <updated>2026-10-04T11:17:04.921035+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>In curl and libcurl 7.52.0 to and including 7.53.1, libcurl would attempt to resume a TLS session even if the client certificate had changed. That is unacceptable since a server by specification is allowed to skip the client certificate check on resume, and may instead use the old identity which was established by the previous certificate (or no certificate). libcurl supports by default the use of TLS session id/ticket to resume previous TLS sessions to speed up subsequent TLS handshakes. They are used when for any reason an existing TLS connection couldn't be kept alive to make the next handshake faster. This flaw is a regression and identical to CVE-2016-5419 reported on August 3rd 2016, but affecting a different version range.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-5v44-xcm9-r9jw"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/gsd-2017-7468</id>
    <title>gsd-2017-7468</title>
    <updated>2026-10-04T11:17:04.921053+00:00</updated>
    <content>gsd-2017-7468</content>
    <link href="https://cve.radiocsirt.org/vuln/gsd-2017-7468"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/opensuse-su-2024:10582-1</id>
    <title>openSUSE-SU-2024:10582-1 — curl-7.79.1-1.1 on GA media</title>
    <updated>2026-10-04T11:17:04.921064+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>curl-7.79.1-1.1 on GA media</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/opensuse-su-2024:10582-1"/>
  </entry>
</feed>
