<?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>Sat, 03 Oct 2026 00:17:02 +0000</lastBuildDate>
    <item>
      <title>Withdrawn: BELL-CVE-2017-2629 — CVE-2017-2629 does not affect BellSoft software</title>
      <link>https://cve.radiocsirt.org/vuln/bell-cve-2017-2629</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/bell-cve-2017-2629</guid>
    </item>
    <item>
      <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>
      <link>https://cve.radiocsirt.org/vuln/certfr-2017-avi-229</link>
      <description>certfr-2017-avi-229</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/certfr-2017-avi-229</guid>
    </item>
    <item>
      <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>
      <link>https://cve.radiocsirt.org/vuln/cleanstart-2026-ay18527</link>
      <description>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: curl&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the curl package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Withdrawn by the publisher.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; CleanStart: curl&lt;/p&gt;
&lt;p&gt;Multiple security vulnerabilities affect the curl package. These issues are resolved in later releases. See references for individual vulnerability details.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cleanstart-2026-ay18527</guid>
    </item>
    <item>
      <title>cnvd-2017-02339</title>
      <link>https://cve.radiocsirt.org/vuln/cnvd-2017-02339</link>
      <description>cnvd-2017-02339</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/cnvd-2017-02339</guid>
    </item>
    <item>
      <title>EUVD-2026-72447</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-72447</link>
      <description>EUVD-2026-72447</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-72447</guid>
    </item>
    <item>
      <title>fkie_cve-2017-2629</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2017-2629</link>
      <description>&lt;p&gt;curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server&amp;#39;s certificate&amp;#39;s validity in the code that checks for a test success or failure. It ends up always thinking there&amp;#39;s valid proof, even when there is none or if the server doesn&amp;#39;t support the TLS extension in question. This could lead to users not detecting when a server&amp;#39;s certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server&amp;#39;s certificate&amp;#39;s validity in the code that checks for a test success or failure. It ends up always thinking there&amp;#39;s valid proof, even when there is none or if the server doesn&amp;#39;t support the TLS extension in question. This could lead to users not detecting when a server&amp;#39;s certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2017-2629</guid>
    </item>
    <item>
      <title>GHSA-7cp4-w7q7-w394</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-7cp4-w7q7-w394</link>
      <description>&lt;p&gt;curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server&amp;#39;s certificate&amp;#39;s validity in the code that checks for a test success or failure. It ends up always thinking there&amp;#39;s valid proof, even when there is none or if the server doesn&amp;#39;t support the TLS extension in question. This could lead to users not detecting when a server&amp;#39;s certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;curl before 7.53.0 has an incorrect TLS Certificate Status Request extension feature that asks for a fresh proof of the server&amp;#39;s certificate&amp;#39;s validity in the code that checks for a test success or failure. It ends up always thinking there&amp;#39;s valid proof, even when there is none or if the server doesn&amp;#39;t support the TLS extension in question. This could lead to users not detecting when a server&amp;#39;s certificate goes invalid or otherwise be mislead that the server is in a better shape than it is in reality. This flaw also exists in the command line tool (--cert-status).&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-7cp4-w7q7-w394</guid>
    </item>
    <item>
      <title>gsd-2017-2629</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2017-2629</link>
      <description>gsd-2017-2629</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2017-2629</guid>
    </item>
    <item>
      <title>openSUSE-SU-2024:10582-1 — curl-7.79.1-1.1 on GA media</title>
      <link>https://cve.radiocsirt.org/vuln/opensuse-su-2024:10582-1</link>
      <description>&lt;p&gt;curl-7.79.1-1.1 on GA media&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;curl-7.79.1-1.1 on GA media&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/opensuse-su-2024:10582-1</guid>
    </item>
    <item>
      <title>WID-SEC-W-2023-1649 — cURL: Schwachstelle ermöglicht Umgehen von Sicherheitsvorkehrungen</title>
      <link>https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1649</link>
      <description>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in cURL ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Ein entfernter, anonymer Angreifer kann eine Schwachstelle in cURL ausnutzen, um Sicherheitsvorkehrungen zu umgehen.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/wid-sec-w-2023-1649</guid>
    </item>
  </channel>
</rss>
