<?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 20:15:20 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-191933</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-191933</link>
      <description>EUVD-2026-191933</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-191933</guid>
    </item>
    <item>
      <title>fkie_cve-2023-40012</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2023-40012</link>
      <description>&lt;p&gt;uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures. Versions of uthenticode prior to the 2.x series did not check Extended Key Usages in certificates, in violation of the Authenticode X.509 certificate profile. As a result, a malicious user could produce a &amp;#34;signed&amp;#34; PE file that uthenticode would verify and consider valid using an X.509 certificate that isn&amp;#39;t entitled to produce code signatures (e.g., a SSL certificate). By design, uthenticode does not perform full-chain validation. However, the absence of EKU validation was an unintended oversight. The 2.0.0 release series includes EKU checks. There are no workarounds to this vulnerability.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;uthenticode is a small cross-platform library for partially verifying Authenticode digital signatures. Versions of uthenticode prior to the 2.x series did not check Extended Key Usages in certificates, in violation of the Authenticode X.509 certificate profile. As a result, a malicious user could produce a &amp;#34;signed&amp;#34; PE file that uthenticode would verify and consider valid using an X.509 certificate that isn&amp;#39;t entitled to produce code signatures (e.g., a SSL certificate). By design, uthenticode does not perform full-chain validation. However, the absence of EKU validation was an unintended oversight. The 2.0.0 release series includes EKU checks. There are no workarounds to this vulnerability.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2023-40012</guid>
    </item>
    <item>
      <title>gsd-2023-40012</title>
      <link>https://cve.radiocsirt.org/vuln/gsd-2023-40012</link>
      <description>gsd-2023-40012</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/gsd-2023-40012</guid>
    </item>
  </channel>
</rss>
